Determining overlap of a parking space by a vehicle

ABSTRACT

A system comprising a computer-readable storage medium storing at least one program and a method for determining vehicle overlap with a parking space is presented. The method may include accessing a set of pixel coordinates defining a location of a vehicle within an image, and translating the set of pixel coordinates to a set of global coordinates defining a geospatial location of the vehicle. The method may further include accessing a set of known coordinates of the parking space. The method may further include determining an overlap amount by comparing the global coordinates of the vehicle with the known global coordinates of the parking space, and determining the vehicle overlaps the parking space based on the overlap amount transgressing a threshold overlap amount. The method may further include updating a data object associated with the vehicle to indicate the vehicle overlaps the parking space.

CROSS REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation of U.S. application Ser. No.15/099,338, titled “DETERMINING OVERLAP OF A PARKING SPACE BY AVEHICLE,” filed Apr. 14, 2016, which claims the benefit of priority toU.S. Provisional Patent Application Ser. No. 62/149,341, titled“INTELLIGENT CITIES—COORDINATES OF BLOB OVERLAP,” filed Apr. 17, 2015,and to U.S. Provisional Patent Application Ser. No. 62/149,345, titled“INTELLIGENT CITIES—REAL-TIME STREAMING AND RULES ENGINE,” filed Apr.17, 2015, and to U.S. Provisional Patent Application Ser. No.62/149,350, titled “INTELLIGENT CITIES—DETERMINATION OF UNIQUE VEHICLE,”filed Apr. 17, 2015, and to U.S. Provisional Patent Application Ser. No.62/149,354, titled “INTELLIGENT CITIES—USER INTERFACES,” filed Apr. 17,2015, and to U.S. Provisional Patent Application Ser. No. 62/149,359,titled “INTELLIGENT CITIES—DATA SIMULATOR,” filed Apr. 17, 2015, each ofwhich is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

The subject matter disclosed herein relates to parking management andparking policy enforcement. In particular, example embodiments relate tosystems and methods for real-time monitoring of parking violations andto providing user interfaces (UIs) to present indications of locationsof parking rule violations.

BACKGROUND

In many municipalities, the regulation and management of vehicle parkingposes challenges for municipal governments. Municipal governmentsfrequently enact various parking policies (e.g., rules and regulations)to govern the parking of vehicles along city streets and other areas. Asan example, time limits may be posted along a street and parking finesmay be imposed on vehicle owners who park their vehicles for longer thanthe posted time. Proper management and enforcement of parking policesprovide benefits to these municipalities in that traffic congestion isreduced by forcing motorists who wish to park for long periods to findsuitable off-street parking, which in turn, creates vacancies for moreconvenient on street parking for user by other motorist who wish to stoponly for short term periods. Further, the parking fines imposed onmotorists who violate parking regulations create additional revenue forthe municipality. However, ineffectively enforcing parking policiesresults in a loss of revenues for the municipalities.

A fundamental technical problem encountered by parking enforcementpersonal in effectively enforcing parking policies is actually detectingwhen vehicles are in violation of a parking policy. Conventionaltechniques for detection of parking policy violations include usingeither parking meter installed adjacent to each parking space or atechnique referred to as “tire-chalking.” Typical parking policyenforcement involves parking enforcement personnel circulating aroundtheir assigned parking zones repetitively to inspect whether parkedvehicles are in violation of parking policies based on either theparking meters indicating that the purchased parking period has expired,or a visual inspection of previously made chalk-marks performed once theparking time limit has elapsed. With either technique, many violationsare missed either because the parking attendant was unable to spot theviolation before the vehicle left or because of motorist improprieties(e.g., by hiding or erasing a chalk-mark).

BRIEF DESCRIPTION OF THE DRAWINGS

Various ones of the appended drawings merely illustrate exampleembodiments of the present inventive subject matter and cannot beconsidered as limiting its scope.

FIG. 1 is an architecture diagram showing a network system having aclient-server architecture configured for monitoring parking policyviolations, according to some embodiments.

FIG. 2 is an interaction diagram illustrating example interactionsbetween components of the network system, according to some embodiments.

FIG. 3 is a block diagram illustrating various modules comprising aparking policy monitoring system, which is provided as part of thenetwork system, according to some embodiments.

FIG. 4 is a data structure diagram illustrating elements of a parkingzone data object, according to some embodiments.

FIG. 5 is a flowchart illustrating a method for creating a new parkingzone with an associated parking policy, according to some embodiments.

FIG. 6 is a flowchart illustrating a method for monitoring parkingpolicy violations, according to some embodiments.

FIG. 7 is a flowchart illustrating additional operations that may beincluded in the method for monitoring parking policy violations,according to some embodiments.

FIG. 8 is a flowchart illustrating a method for determining occupancy ofa parking space by a vehicle, according to some embodiments.

FIG. 9 is a flowchart illustrating a method for determining whether avehicle overlaps a parking space, according to some embodiments.

FIG. 10 is a flowchart illustrating a method for determining whether avehicle overlaps a parking space, according to some alternativeembodiments.

FIG. 11 is a flowchart illustrating a method for determining whether avehicle is stationary or in motion, according to some embodiments.

FIG. 12 is a flowchart illustrating a method for tracking a movingvehicle, according to some embodiments.

FIGS. 13A-13F are interface diagrams illustrating portions of an exampleUI for creating or modifying a parking zone, according to someembodiments.

FIGS. 14A-14D are interface diagrams illustrating portions of an exampleUI for monitoring parking rule violations in a parking zone, accordingto some embodiments.

FIGS. 15A-15B are interface diagrams illustrating portions of an exampleUI for monitoring parking rule violations in a parking zone, accordingto some embodiments.

FIG. 16 is an interface diagram illustrating an example UI formonitoring parking space occupancy in a parking zone, according to someembodiments.

FIG. 17 is an interface diagram illustrating an example UI forpresenting an overview of parking information of a municipality,according to some embodiments.

FIG. 18 is a diagrammatic representation of a machine in the exampleform of a computer system within which a set of instructions for causingthe machine to perform any one or more of the methodologies discussedherein may be executed.

DETAILED DESCRIPTION

Reference will now be made in detail to specific example embodiments forcarrying out the inventive subject matter. Examples of these specificembodiments are illustrated in the accompanying drawings, and specificdetails are set forth in the following description in order to provide athorough understanding of the subject matter. It will be understood thatthese examples are not intended to limit the scope of the claims to theillustrated embodiments. On the contrary, they are intended to coversuch alternatives, modifications, and equivalents as may be includedwithin the scope of the disclosure.

Aspects of the present disclosure involve systems and methods formonitoring parking policy violations. In example embodiments, data isstreamed from multiple camera nodes to a parking policy managementsystem where the data is processed to determine if parking spaces areoccupied and if vehicles occupying the parking spaces are in violationof parking policies. The data streamed by the camera nodes includesmetadata that includes information describing images (also referred toherein as “parking metadata”) captured by the camera nodes along withother information related to parking space occupancy. Each camera nodemay be configured such that the images captured by the node show atleast one parking space, and in some instances, vehicles parked in theparking spaces, or in motion near the parking spaces. Each camera nodeis specially configured (e.g., with application logic) to analyze thecaptured images to provide pixel coordinates of vehicles in the image aspart of the metadata along with a timestamp, a camera identifier, alocation identifier, and a vehicle identifier.

The metadata provided by the camera nodes may be sent via a messagingprotocol to a messaging queue of the parking policy management systemwhere back-end analytics store the pixel coordinate data in a persistentformat to a back-end database. Sending the metadata rather than theimages themselves provides the ability to send locations of parked ormoving vehicles in great numbers for processing and removes dependencyon camera modes to send images in bulk for processing. Further, bysending the metadata rather than the images, the system reduces theamount of storage needed to process parking rule validations.

Parking policies discussed herein may include a set of parking rulesthat regulate the parking of vehicles in the parking spaces. The parkingrules may, for example, impose time constraints (e.g., time limits) onvehicles parked in parking spaces. The processing performed by theparking policy management system includes performing a number ofvalidations to determine whether the parking space is occupied andwhether the vehicle occupying the space is in violation of one or moreparking rules included in the parking policy. In performing thesevalidations, the parking policy management system translates the pixelcoordinates of vehicles received from the camera nodes into globalcoordinates (e.g., real-world coordinates) and compares the globalcoordinates of the vehicles to known coordinates of parking spaces. Theparking policy management system may process the data in real-time or inmini batches of data at a configurable frequency.

The parking policy management system includes a parking rules engine toprocess data streamed from multiple camera nodes to determine, inreal-time, if a parked vehicle is in violation of a parking rule. Theparking rules engine provides the ability to run complex parking ruleson real-time streaming data, and flag data if a violation is found inreal-time. The parking rules engine may further remove dependency oncamera nodes to determine if a vehicle is in violation. Multiple rulesmay apply for a parking space or zone and the parking rules engine maydetermine which rules apply based on the timestamp and other factors.The parking rules engine enables complex rule processing to occur usingthe data streamed from the camera nodes and the parking spaces or zonesstored rules data.

By processing the data in the manner described above, the parking policymanagement system provides highly efficient real-time processing of data(e.g., metadata describing image data) from multiple camera nodes.Further, the parking policy management system may increase the speedwith which parking violations are identified, and thereby reduce costsin making such determinations.

Additional aspects of the present disclosure involve tracking movingvehicles appearing in multiple images received from different cameras.As an example, cameras may be mounted on street light poles to have aview of the street, which allows the cameras to record images of traffic(e.g., moving vehicles) on the street. The same moving vehicle mayappear in multiple images captured by the cameras, and the cameras haveoverlapping views. Each of the cameras transmits parking metadata to theparking policy management system where the parking metadata is processedto identify the same moving vehicle appearing in the multiple images.Upon determining that the vehicle is moving and that the same vehicle isshown in the multiple images, the parking policy management systemconverts pixel coordinates (e.g., included in the parking metadata) ofthe vehicle to global coordinates (e.g., geospatial coordinates), andstores a record of the locations defined by the global coordinates so asto track each location passed or visited by the vehicle. For example,the parking policy management system may plot the location of vehicleson a geospatial map to track movement of traffic. The traffic movementmay be displayed on a user interface, and various analytics may beperformed to provide alerts and data points to assist municipalities toresolve traffic issues or assist with city planning. In this way,municipalities that face challenging traffic congestions, which resultsin loss of income, safety hazards, and a decreasing in life quality ofits citizens, may be provided with the ability to track traffic so thatthe municipalities may make better decisions and provide alerts toofficials and citizens.

Additional aspects of the present disclosure involve UIs provided by theparking policy management system to show real-time parking spaceoccupancy and parking policy violations on a geospatial map. Users suchas parking attendants can use the UIs of the parking policy managementsystem to identify locations of parking violations and review furtherinformation for each violation such as an addresses of the violation,parking rules being violated, a timing of the violation, images of thevehicle in violation of the parking, and information about the vehicles(e.g., make, model, color, and license plate number).

Additional aspects of the present disclosure involve UIs to create andedit parking zones with associated parking policies. Each parking zoneincludes at least one parking space. The UIs may provide users with theability to specify parking zone locations. For example, users maymanually enter coordinates of parking space or users may trace theoutline of a parking zone location on a geospatial map presented as partof the UI. The UI may further allow users to define a parking policyassociated with the parking zone that includes one or more parkingrules. Users may also use such UIs to associate cameras with the parkingzone so as to facilitate a linking between parking zones and the camerasthat record images of portions of the parking zone.

FIG. 1 is an architecture diagram showing a network system 100 having aclient-server architecture configured for monitoring parking policyviolations, according to an example embodiment. While the network system100 shown in FIG. 1 may employ a client-server architecture, the presentinventive subject matter is, of course, not limited to such anarchitecture, and could equally well find application in anevent-driven, distributed, or peer-to-peer architecture system, forexample. Moreover, it shall be appreciated that although the variousfunctional components of the network system 100 are discussed in thesingular sense, multiple instances of one or more of the variousfunctional components may be employed.

As shown, the network system 100 includes a parking policy managementsystem 102, a client device 104, and a camera node 106, allcommunicatively coupled to each other via a network 108. The parkingpolicy management system 102 may be implemented in a special-purpose(e.g., specialized) computer system, in whole or in part, as describedbelow.

Also shown in FIG. 1 is a user 110, who may be a human user (e.g., aparking attendant, parking policy administrator, or other such parkingenforcement personnel), a machine user (e.g., a computer configured by asoftware program to interact with the client device 104), or anysuitable combination thereof (e.g., a human assisted by a machine or amachine supervised by a human). The user 110 is associated with theclient device 104 and may be a user of the client device 104. Forexample, the client device 104 may be a desktop computer, a vehiclecomputer, a tablet computer, a navigational device, a portable mediadevice, a smart phone, or a wearable device (e.g., a smart watch, smartglasses, smart clothing, or smart jewelry) belonging to the user 110.

The client device 104 may also include any one of a web client 112 orapplication 114 to facilitate communication and interaction between theuser 110 and the parking policy management system 102. In variousembodiments, information communicated between the parking policymanagement system 102 and the client device 104 may involveuser-selected functions available through one or more user interfaces(UIs). The UIs may be specifically associated with the web client 112(e.g., a browser) or the application 114. Accordingly, during acommunication session with the client device 104, the parking policymanagement system 102 may provide the client device 104 with a set ofmachine-readable instructions that, when interpreted by the clientdevice 104 using the web client 112 or the application 114, cause theclient device 104 to present the UI, and transmit user input receivedthrough such UIs back to the parking policy management system 102. As anexample, the UIs provided to the client device 104 by the parking policymanagement system 102 allow users to view information regarding parkingspace occupancy and parking policy violations overlaid on a geospatialmap.

The network 108 may be any network that enables communication between oramong systems, machines, databases, and devices (e.g., between parkingpolicy management system 102 and the client device 104). Accordingly,the network 108 may be a wired network, a wireless network (e.g., amobile or cellular network), or any suitable combination thereof. Thenetwork 108 may include one or more portions that constitute a privatenetwork, a public network (e.g., the Internet), or any suitablecombination thereof. Accordingly, the network 108 may include one ormore portions that incorporate a local area network (LAN), a wide areanetwork (WAN), the Internet, a mobile telephone network (e.g., acellular network), a wired telephone network (e.g., a plain oldtelephone system (POTS) network), a wireless data network (e.g., a WiFinetwork or WiMax network), or any suitable combination thereof. Any oneor more portions of the network 108 may communicate information via atransmission medium. As used herein, “transmission medium” refers to anyintangible (e.g., transitory) medium that is capable of communicating(e.g., transmitting) instructions for execution by a machine (e.g., byone or more processors of such a machine), and includes digital oranalog communication signals or other intangible media to facilitatecommunication of such software.

The camera node 106 includes a camera 116 and node logic 118. The camera116 may be any of a variety of image capturing devices configured forrecording images (e.g., single images or video). The camera node 106 maybe or include a street light pole, and may be positioned such that thecamera 116 captures images of a parking space 120. The node logic 118may configure the camera node 106 to analyze the images 120 recorded bythe camera 116 to provide pixel coordinates of a vehicle 122 that may beshown in an image 124 along with the parking space 120. The camera node106 transmits data packets that include parking metadata 126 thatincludes the pixel coordinates of the vehicle 122 to the parking policymanagement system 102 (e.g., via a messaging protocol) over the network108. The parking policy management system 102 uses the pixel coordinatesincluded in the parking metadata 122 received from the camera node 106to determine whether the vehicle 122 is occupying (e.g., parked in) theparking space 120. For as long as the vehicle 122 is included in imagesrecorded by the camera 116, the camera node 106 continues to transmitthe pixel coordinates of the vehicle 122 to the parking policymanagement system 102, and the parking policy management system 102 usesthe pixel coordinates to monitor the vehicle 122 to determine if thevehicle 122 is in violation of one or more parking rules included in aparking policy that is applicable to the parking space 120.

FIG. 2 is an interaction diagram illustrating example interactionsbetween components of the network system 100, according to someembodiments. In particular, FIG. 2 illustrates example interactions thatoccur between the parking policy management system 102, client device104, and the camera node 106 as part of monitoring parking policyviolations occurring with respect to the parking space 122.

As shown, at operation 202 the camera 116 of the camera node 106 recordsan image 124. As noted above, the camera 116 is positioned such that thecamera 116 records images that show the parking space 120. The image 124recorded by the camera 116 may further show the vehicle 122 that, uponinitial processing, appears to the camera node 106 as a “blob” in theimage 124.

At operation 204, the node logic 118 configures the camera node 106 toperform image analysis on the image 124 to determine the pixelcoordinates of the blob. The pixel coordinates are a set of spatialcoordinates that identify the location of the blob within the imageitself.

At operation 206, the camera node 106 transmits the parking metadata 126(e.g., including information describing the recorded image 124) over thenetwork 108 to the parking policy management system 102. The camera node106 may transmit the metadata 126 as a data packet using a standardmessaging protocol. The parking metadata 126 includes the pixelcoordinates of the blob (e.g., the vehicle 122) along with a timestamp(e.g., a date and time the image was recorded), a camera identifier(e.g., identifying the camera 116), a location identifier (e.g.,identifying the camera node 106 or a location of the camera node 106),and a blob identifier (e.g., a unique identifier assigned to the vehicle122). The camera node 106 may continuously transmit (e.g., atpredetermined intervals) the parking metadata while the vehicle 122continues to be shown in image recorded by the camera 116.

At operation 208, the parking policy management system 102 receives thedata packet and persists (e.g. saves) the parking metadata 126 to a datastore (e.g., a database). In persisting the parking metadata 126 to thedata store, the parking policy management system 102 may create ormodify a data object associated with the camera node 106 or the parkingspace 120. The created or modified data object includes the receivedparking metadata 126. As the camera node 106 continues to transmitsubsequent parking metadata, the parking policy management system 102may store the subsequent parking metadata received from the camera node106 in the same data object or in another data object that is linked tothe same data object. In this way, the parking policy management system102 maintains a log of parking activity with respect to the parkingspace 120. It shall be appreciated that the parking policy managementsystem 102 may be communicatively coupled to multiple instances of thecamera node 106 that record images showing other parking spaces, and theparking policy management system 102 may accordingly maintain separaterecords for each camera node 106 and/or parking spaces so as to maintaina log of parking activity with respect to a group of parking spaces.

At operation 210, the parking policy management system 102 processes theparking metadata 126 received from the camera node 106. The processingof the parking metadata 126 may, for example, include determining anoccupancy status of the parking space 120. The occupancy status of theparking space 120 may be either occupied (e.g., a vehicle is parked inthe parking space) or unoccupied (e.g., no vehicle is parked in theparking space). Accordingly, the determining of the occupancy status ofthe parking space 120 includes determining whether the vehicle 122 isparked in the parking space 120. In determining that the vehicle 122 isparked in the parking space 120, the parking policy management system102 verifies that the location of the vehicle 122 overlaps the locationof the parking space 120, and the parking policy management system 102further verifies that the vehicle is still (e.g., not in motion). If theparking policy management system 102 determines the vehicle 122 is inmotion, the parking policy management system 102 flags the vehicle 122for further monitoring.

Upon determining that the parking space 120 is occupied by the vehicle122 (e.g., the vehicle 122 is parked in the parking space 120), theparking policy management system 102 determines whether the vehicle 122is in violation of a parking rule that is applicable to the parkingspace 120. In determining whether the vehicle is in violation of aparking rule, the parking policy management system 102 monitors furthermetadata transmitted by the camera node 106 (e.g., metadata describingsubsequent images captured by the camera 116). The parking policymanagement system 102 further accesses a parking policy specificallyassociated with the parking space 120. The parking policy includes oneor more parking rules. The parking policy may include parking rules thathave applicability only to certain times of day, or days of the week,for example. Accordingly, the determining of whether the vehicle is inviolation of a parking rule includes determining which, if any, parkingrules apply, and the applicability of parking rules may be based on thecurrent time of day or current day of the week.

Parking rules may, for example, impose a time limit on parking in theparking space 120. Accordingly, the determining of whether the vehicle122 is in violation of a parking rule may include determining an elapsedtime since the vehicle first parked in the parking space 120, andcomparing the elapsed time to the time limit imposed by the parkingrule.

At operation 212, the parking policy management system 102 generatespresentation data corresponding to a user interface. The presentationdata may include a geospatial map of the area surrounding the parkingspace 120, visual indicators of parking space occupancy, visualindicators of parking rule violations, visual indicators of locationsvisited by the vehicle 122 (e.g., if vehicle 122 is determined to be inmotion), identifiers of specific parking rules being violated, images ofthe vehicle 122, and textual information describing the vehicle (e.g.,make, model, color, and license plate number). Accordingly, ingenerating the presentation data, the parking policy management system102 may retrieve, from the camera node 106, the first image showing thevehicle 122 parked in the parking space 120 (e.g., the first image fromwhich the parking policy management system 102 can determine the vehicle122 is parked in the parking space 120), and a subsequent image fromwhich the parking monitoring 102 determined that the vehicle 122 is inviolation of the parking rule (e.g., the image used to determine thevehicle 122 is in violation of the parking rule). The UI may include thegeospatial map overlaid with visual indicators of parking spaceoccupancy and parking rule violations that may be selectable (e.g.,through appropriate user input device interaction with the UI) topresented additional UI elements that include the images of the vehicle122, and textual information describing the vehicle.

At operation 214, the parking policy management system 102 transmits thepresentation data to the client device 104 to enable the client device104 to present the UI on a display of the client device 104. Uponreceiving the presentation data, the client device 104 may temporarilystore the presentation data to enable the client device to display theUI, at operation 216.

FIG. 3 is a block diagram illustrating various modules comprising aparking policy management system 100, which is provided as part of thenetwork system, according to some embodiments. To avoid obscuring theinventive subject matter with unnecessary detail, various functionalcomponents (e.g., modules, engines, and databases) that are not germaneto conveying an understanding of the inventive subject matter have beenomitted from FIG. 2. However, a skilled artisan will readily recognizethat various additional functional components may be supported by theparking policy management system 102 to facilitate additionalfunctionality that is not specifically described herein.

As shown, the parking policy management system 102 includes: aninterface module 300; a data intake module 302; a policy creation module304; a unique vehicle identification module 306; a coordinatetranslation module 308; an occupancy engine 310 comprising an overlapmodule 312 and a motion module 314; a parking rules engine 316; and adata store 318. Each of the above referenced functional components ofthe parking policy management system 102 are configured to communicatewith each other (e.g., via a bus, shared memory, a switch, orapplication programming interfaces (APIs)). Any one or more offunctional components illustrated in FIG. 3 and described herein may beimplemented using hardware (e.g., a processor of a machine) or acombination of hardware and software. For example, any module describedherein may configure a processor to perform the operations describedherein for that module. Moreover, any two or more of these modules maybe combined into a single module, and the functions described herein fora single module may be subdivided among multiple modules. Furthermore,according to various example embodiments, any of the functionalcomponents illustrated in FIG. 3 may be implemented together orseparately within a single machine, database, or device may bedistributed across multiple machines, databases, or devices.

The interface module 300 receives requests from the client device 104,and communicates appropriate responses to the client device 104. Theinterface module 300 may receive requests from devices in the form ofHypertext Transfer Protocol (HTTP) requests or other web-based, APIrequests. For example, the interface module 300 provides a number ofinterfaces (e.g., APIs or UIs that are presented by the device 104) thatallow data to be received by the parking policy management system 102.

For example, the interface module 300 may provide a policy creation UIthat allows the user 110 of the client device 104 to create parkingpolicies (e.g., a set of parking rules) associated with a particularparking zone (e.g., a set of parking spaces). The interface module 300also provides parking attendant UIs to the client device 104 to assistthe user 110 (e.g., parking attendants or other such parking enforcementpersonnel) in monitoring parking policy violations in their assignedparking zone. To provide a UI to the client device 104, the interfacemodule 300 transmits presentation data to the client device 104 thatenables the client device 104 to present the UI on a display of theclient device 104. In some embodiments, the interface module 300 maytransmit the presentation data to the client device 104 along with a setof instructions to display the presentation data. The client device 104may temporarily store the presentation data to enable display of the UI.

The UIs provided by the interface module 300 may include various maps,graphs, tables, charts, and other graphics used, for example, to provideinformation related to parking space occupancy and parking policyviolations. The interfaces may also include various input controlelements (e.g., sliders, buttons, drop-down menus, check-boxes, and dataentry fields) that allow users to specify various inputs, and theinterface module 300 receives and processes user input received throughsuch input control elements.

The data intake module 302 is responsible for obtaining data transmittedfrom the camera node 106 to the parking policy management system 102.For example, the data intake module 302 may receive data packets thatinclude parking metadata (e.g., parking metadata 126) from the cameranode 106. The data packets may, for example, be transmitted by thecamera node 106 using a messaging protocol and upon receipt, the dataintake module 302 may add the parking metadata from the data packet to amessaging queue (e.g., maintained in the data store 318) for subsequentprocessing. The data intake module 302 may persist the parking metadatato one or more data objects stored in the data store 318. For example,the data intake module 302 may modify a data object associated with thecamera 106, the parking space 120, or the vehicle 122 to include thereceived parking metadata 126.

In some instances, multiple cameras (e.g., multiple instances of camera116) may record an image (e.g., image 124) of the parking space 120 andthe vehicle 122. In these instances, the data intake module 302 mayanalyze the metadata associated with each of the images to determinewhich image to use for processing. More specifically, the data intakemodule 302 analyzes parking metadata for multiple images, and based on aresult of the analysis, the data intake module 302 selects a singleinstance of parking metadata (e.g., a single set of pixel coordinates)to persist in the data store 318 for association with the parking space120 or the vehicle 122.

The data intake module 302 may be further configured to retrieve actualimages recorded by the camera 116 of the camera node 106 (or otherinstances of these components) for us by the interface module 300 ingenerating presentation data that represents a UI. For example, upondetermining that the vehicle 122 is in violation of a parking ruleapplicable to the parking space 120, the data intake module 302 mayretrieve two images from the camera node 106—a first image correspondingto first parking metadata used to determine the vehicle 122 is parked inthe parking space 120 and a second image corresponding to second parkingmetadata used to determine the vehicle 122 is in violation of theparking rule applicable to the parking space 120.

The policy creation module 304 is responsible for creating and modifyingparking policies associated with parking zones. More specifically, theparking creation module 304 may be utilized to create or modify parkingzone data objects (e.g., parking zone data object 400) that includeinformation describing parking policies associated with a parking zone.In creating and modifying parking zone data objects, the policy creationmodule 304 works in conjunction with the interface module 300 to receiveuser specified information entered into various portions of the policycreation UI. For example, a user may specify a location of a parkingzone (or a parking space within the parking zone) by tracing an outlineof the location on a geospatial map included in a parking zone creatinginterface provided by the interface module 300. The policy creationmodule 304 may convert the user input (e.g., the traced outline) to aset of global coordinates (e.g., geospatial coordinates) based on theposition of the outline on the geospatial map. The policy creationmodule 304 incorporates the user-entered information into a parking zonedata object associated with a particular parking zone and persists(e.g., stores) the parking zone data object in the data store 318.

The unique vehicle identification module 306 is responsible foridentifying unique vehicles shown in multiple images recorded bymultiple cameras. In other words, the unique vehicle identificationmodule 306 may determine that a first blob shown in a first image is thesame as a second blob shown in the second image, and that both of whichcorrespond to the same vehicle (e.g., vehicle 122). In determining thevehicle 122 is shown in both images, the unique vehicle identificationmodule 306 access known information (e.g., from the data store 318)about the angle, height, and position of the first and second camerausing unique camera identifiers included in metadata of the images.Using the known information about the physical orientation of the firstand second camera such as angle, height, and position of the first andsecond camera, the unique vehicle identification module 306 compares thelocations of the blobs (e.g., geo-graphic locations represented by a setof global coordinates) to determine if the difference in location of theblobs is below an allowable threshold. The allowable threshold may, forexample, be based on an expected trajectory of a vehicle in the area ofthe first and second camera based on speed limits, traffic conditions,and other such factors. Based on the determined location differencebeing below the allowable threshold, the unique vehicle identificationmodule 306 determines the blob (e.g., vehicle) shown in the first imageis also the blob (e.g., vehicle) shown in the second image.

The coordinate translation module 308 is responsible for translatingpixel coordinates (e.g., defining a location in the image space) toglobal coordinates (e.g., defining a geo-graphic location in thereal-world). As noted above, the camera node 106 transmits parkingmetadata 126 to the parking policy management system 102 that includes aset of pixel coordinates that define a location of a blob (e.g., vehicle122) within the image space. The coordinate translation module 308 isthus responsible for mapping the location of the blob (e.g., vehicle122) within the image space to a geo-graphic location in the real-worldby converting the set of pixel coordinates to a set of global (e.g.,geo-graphic) coordinates. In converting pixel coordinates to globalcoordinates, the coordinate translation module 308 may use the knownangle, height, and position of the camera that recorded the image (e.g.,included in a data object associated with the camera and maintained inthe data store 318) in conjunction with a homography matrix to determinethe corresponding global coordinates. The coordinate translation module308 may further persist each set of global coordinates to a data objectassociated with either the parking space 120 or vehicle 122, or both.

The occupancy engine 310 is responsible for determining occupancy statusof parking spaces. The occupancy engine 310 may determine the occupancystatus of parking spaces based on an analysis of parking metadataassociated with the parking space. The occupancy status refers towhether a parking space is occupied (e.g., a vehicle is parked in theparking space) or unoccupied (e.g., no vehicle is parked in the parkingspace). As an example, the occupancy engine 310 may analyze the parkingmetadata 126 to determine whether the parking space 120 is occupied bythe vehicle 122.

In determining the occupancy status of the parking space 120, theoccupancy engine 310 may invoke the functionality of the overlap module312 the motion module 314. The overlap module 312 is responsible fordetermining whether the location of a blob shown in an image overlaps(e.g., covers) a parking space based on image data describing the image.For example, the overlap module 312 determines whether the location ofthe vehicle 122 overlaps the location of the parking space 120 based onthe parking metadata 126. The overlap module 312 determines whether theblob overlaps the parking space based on a comparison of a location ofthe blob (e.g., as represented by or derived from the set of pixelcoordinates of the blob included in the parking metadata) and knownlocation of the parking space (e.g., included in a data objectassociated with the parking space). In comparing the two locations, theoverlap module 312 may utilize centroid logic 320 to compute anarithmetic mean of the locations of the blob and the parking spacerepresented by sets of coordinates (e.g., either global or pixel)defining the location of each.

The motion module 314 is responsible for determining whether blob (e.g.,a vehicle) shown in images are in motion. The motion module 314determines whether a blob shown in an image is in motion by comparinglocations of the blob from parking metadata of multiple images. Forexample, the motion module 314 may compare a first set of pixelcoordinates received from the camera node 106 corresponding to thelocation of the vehicle 122 in a first image with a second set of pixelcoordinates received from the camera node 106 corresponding to thelocation of the blob in a second image, and based on the resultingdifference in location transgressing a configurable threshold, themotion module 314 determines that the vehicle 122 is in motion. Themotion module 314 may also utilize the centroid logic 320 in comparingthe sets of pixel locations to determine the difference in location ofthe vehicle 122 in the two images.

If the motion module 314 determines that the vehicle 122 is in motion,the motion module 314 adds the locations of the vehicle 122 (e.g.,derived from the sets of pixel coordinates) to a data object associatedwith the vehicle 122 and flags the vehicle 122 for further monitoring.Furthermore, if the motion module 314 determines that the vehicle 122 isin motion, or if the overlap module 312 determines that the location ofthe vehicle 122 does not overlap the location of the parking space 120,the occupancy engine 310 determines that the occupancy status of theparking space 120 is “unoccupied.” If the motion module 314 determinesthat the vehicle 122 is stationary (e.g., not in motion) and the overlapmodule 312 determines the location of the vehicle 122 overlaps thelocation of the parking space 120, the occupancy engine 310 determinesthat the occupancy status of the parking space 120 is “occupied.”

The parking rules engine 316 is responsible for determining parking ruleviolations based on parking metadata. As an example, in response to theoccupancy engine 310 determining that the parking space 120 is occupiedby the vehicle 122, the parking rules engine 316 checks whether thevehicle 122 is in violation of a parking rule included in a parkingpolicy associated with the parking space. In determining whether thevehicle 122 is in violation of a parking rule, the parking rules engine316 accesses a parking zone data object associated with the parking zonein which the parking space is located. The parking zone data objectincludes the parking policy associated with the parking zone. Theparking policy may include a set of parking rules that limit parking inthe parking zone. Parking rules may be specifically associated withparticular parking spaces, and may have limited applicability to certainhours of the day, days of the week, or days of the year. Accordingly, indetermining whether the vehicle 122 is in violation of a parking rule,the parking rules engine 316 determines which parking rules from theparking policy are applicable based on comparing a current time withtiming attributes associated with each parking rule. Some parking rulesmay place a time limit on parking in the parking space 120, and thus,the parking rules engine 316 may determine whether the vehicle 122 is inviolation of a parking rule based on an elapsed time of the vehicle 122being parked in the parking space 120 exceeding the time limit imposedby one or more parking rules.

The data store 318 stores data objects pertaining to various aspects andfunctions of the parking policy management system 102. For example, thedata store 318 may store: camera data objects including informationabout cameras such as an camera identifier, and orientation informationsuch as angles, height, and position of the camera; parking zone dataobjects including information about known geospatial locations (e.g.,represented by global coordinates) of parking spaces in the parkingzone, known locations of parking spaces within images recorded bycameras in the parking zone (e.g., represented by pixel coordinates),and parking policies applicable to the parking zone; and vehicle dataobjects including an identifier of the vehicle, locations of thevehicle, images of the vehicle, and records of parking policy violationsof the vehicle. Within the data store 318, camera data objects may beassociated with parking zone data objects so as to maintain a linkagebetween parking zones and the cameras that record images of parkingspaces and vehicles in the parking zone. Further, vehicle data objectsmay be associated with parking zone data objects so as to maintain alinkage between parking zones and the vehicles parked in a parking spacein the parking zone. Similarly, camera data objects may be associatedwith vehicle data objects so as to maintain a linkage between camerasand the vehicles shown in images recorded by the cameras.

As more detailed example of the data objects that may be stored in thedata store 318, FIG. 4 is a data structure diagram illustrating elementsof a parking zone data object 400, according to some embodiments. Theparking zone data object 400 is a data structure stored in the datastore 318 of the parking policy management system 102. The parking zonedata object 400 includes multiple fields for maintaining pertinentinformation describing a parking policy associated with a parking zone.For example, the parking zone data object 400 includes an identifier 402that uniquely identifies the parking zone. The identifier 402 may beassigned to the parking zone by the parking policy management system 102upon creation of the parking zone data object 400.

The parking zone data object 400 also includes a description 404 of theparking zone. The description 404 may, for example, include ahuman-generated (e.g., user 110) textual description of the parkingzone.

The parking zone data object 400 also includes location data 406describing a location of the parking zone. The location data 406 mayinclude a set of geospatial coordinates that define the perimeter of theparking zone (e.g., by providing a coordinate pair for each corner ofthe parking zone). Each parking zone may include one or more parkingspaces, and as such, the location data 406 may include informationdescribing the location of each parking space in the parking zone. Inparticular, the location data 406 includes a set of geospatialcoordinates (e.g., global coordinates) for each parking space in theparking zone. The location data 406 may, in some embodiments, include aset of pixel coordinates for each parking space that define a locationof each parking space in images recorded by nearby cameras.

The parking zone data object 400 further includes a parking policy 408.The parking policy includes a set of parking rules that are applicableto the parking zone. The parking rules include limits on parking in theparking zone. For example, a parking rule may impose a time limit onparking in the parking zone (e.g., two hour maximum). Individual parkingrules may be specifically associated with a particular parking space orset of parking spaces in the parking zone, or may be generallyassociated with the entire parking zone. Each parking rule may have aone or more temporal attributes that temporally limit the applicabilityof the rule. For example, a particular parking rule may be applicableduring certain hours of the day (e.g., from 6:00 AM to 6:00 PM), certaindays of the week (e.g., Wednesdays), or certain days of the year (e.g.,holidays).

The parking zone data object 400 may further include a field for cameraidentifiers 410. The camera identifiers 410 field includes identifiersof cameras (e.g., instances of camera 116) that record images of parkingspaces in the parking zone. In some instances, a parking zone may haveonly a single camera that records images of the parking zone, and thecamera identifiers 410 field includes only a single identifier. In otherinstances, a parking zone may have multiple cameras that record imagesof the parking zone, and the camera identifiers 410 field includesmultiple identifiers.

FIG. 5 is a flowchart illustrating a method 500 for creating a newparking zone with an associated parking policy, according to someembodiments. The method 500 may be embodied in computer-readableinstructions for execution by one or more processors such that theoperations of the method 500 may be performed in part or in whole by theparking policy management system 102; accordingly, the method 500 isdescribed below by way of example with reference thereto. However, itshall be appreciated that at least some of the operations of the method500 may be deployed on various other hardware configurations and themethod 500 is not intended to be limited to the parking managementsystem 102.

At operation 505, the interface module 300 causes display of a parkingzone creation UI on the client device 104. The parking zone creation UIincludes a number of data input elements (e.g., text fields, drop-downmenus, and buttons) for receiving information describing a parkingpolicy associated with a particular parking zone. The parking zonecreation UI may further include a geospatial map configured to receiveuser input (e.g., through appropriate interaction with an input device)specifying a location of a parking zone.

In causing presentation of the UI, the interface module 300 may transmitpresentation data to the client device 104 to cause the client device104 to present the UI on a display of the client device 104. Uponreceiving the presentation data, the client device 104 may temporarilystore the presentation data to enable the client device to display theUI.

At operation 510, the policy creation module 304 receives, from theclient device 104, a human-generated parking zone description enteredvia the parking zone creation UI. The parking zone description includesa textual description of the parking zone.

At operation 515, the policy creation module 304 receives, from theclient device 104, parking zone location data entered via the parkingzone creation UI. The parking zone location data includes informationdescribing a location of the parking zone and locations of each parkingspace within the parking zone. In some embodiments, the user 110 mayenter the location data using input elements in the UI such as drop-downmenus or text input boxes. For example, the user 110 may use text inputboxes to specify a set of global coordinates (e.g., geospatialcoordinates) for each parking space in the parking zone (e.g., acoordinate pair for each corner of the parking space).

In other embodiments, the user 110 may specify the location of theparking zone and parking space included therein by providing inputdirectly to the geospatial map displayed within the policy creation UIthat specifies a location of the parking zone or a particular parkingspace. For example, the user 110 may manipulate a mouse cursor (e.g.,through physical interaction with a mouse) or use a touch-based gesture(e.g., for devices with touch-based displays) to trace an outline of thelocation of the parking space on the geospatial map. Upon receiving theuser 110's input on the geospatial map (e.g., the traced outline of theparking zone), the policy creation module 304 converts the input to oneor more sets of global coordinates (e.g., geo-graphic coordinates) basedon the position of the outline of the parking zone on the geospatialmap.

At operation 520, the policy creation module 304 generates a parkingzone data object (e.g., the parking zone data object 400) for theparking zone defined by the received location data. As noted above, theparking zone data object is a data structure that includes informationdescribing the parking policy for the parking zone. In generating theparking zone data object, the policy creation module 304 mayautomatically assign (e.g., without further user intervention) anidentifier to the parking zone that uniquely identifies the parkingzone.

At operation 525, the policy creation module 304 receives, from theclient device 104, a parking policy definition entered using the parkingzone creation UI. The parking definition defines the parking policyassociated with the parking zone defined by the received location data.The parking policy definition may be entered using a variety ofgraphical elements such as drop-down menus or text entry fields.

Each parking policy includes a set of parking rules, and each rule mayinclude a temporal attribute that temporally limits the applicability ofthe rule. The user 110 may, for example, select individual parking rulesfrom a drop-down menu that includes a list of predefined parking rules.Parking rules may, for example, correspond to parking regulationcodified in a municipal or cited code. The user 110 may, for example,specify temporal attributes for each selected parking rule using anadditional UI element (e.g., drop-down menu or date picker) displayed inthe parking creation interface in conjunction with the drop-down menu ofpredefined parking rules, and the user interface module 300 may receivethe user-specified temporal attributes and provide them to the policycreation module 304 for association with the corresponding parking rule.

At operation 530, the policy creation module 304 modifies (e.g.,augments) the parking zone data object to include the parking policydefined by the parking policy definition received from the user 110. Forexample, the policy creation module 304 may store the set of rulescomposing the parking policy in a parking policy field (e.g., parkingpolicy 408) of the parking zone data object.

At operation 535, the policy creation module 304 receives, from theclient device 104, one or more camera identifiers entered via the policycreation interface. Each camera identifier uniquely identifies a camera(e.g., camera 116) that records images showing at least a portion of theparking zone.

At operation 540, the policy creation module 304 associates the one ormore camera identifiers with the parking zone data object. Theassociating of a camera identifier with the parking zone data objectincludes electronically linking the parking zone data object with adifferent data object associated with the camera identifier (e.g., adata object storing information describing the identified camera). Theelectronic linking may include modifying (e.g., augmenting) the parkingzone data object to include the camera identifier (e.g., storing thecamera identifier in the camera identifiers 410 field of the parkingzone data object 400).

At operation 545, the policy creation module 304 persists (e.g., stores)the parking zone data object in the data store 318 of the parking policymanagement system 102. In this way, the parking policy management system102 may subsequently access parking zone data object to determineparking space occupancy and parking rule violation in connection withthe parking spaces included in the parking zone.

FIG. 6 is a flowchart illustrating a method 600 for monitoring parkingpolicy violations, according to some embodiments. The method 600 may beembodied in computer-readable instructions for execution by one or moreprocessors such that the operations of the method 600 may be performedin part or in whole by the parking policy management system 102;accordingly, the method 600 is described below by way of example withreference thereto. However, it shall be appreciated that at least someof the operations of the method 600 may be deployed on various otherhardware configurations and the method 600 is not intended to be limitedto the parking management system 102.

At operation 605, occupancy engine 310 accesses parking metadataassociated with an image recorded by the camera node 106. As notedabove, the camera node 106 is positioned such that the camera 116records images of the parking space 120. The parking metadata includes aset of pixel coordinates corresponding to a blob (e.g., a polygon) shownin the image along with the parking space 120. The set of coordinatesinclude a coordinate pair (e.g., an X-axis value and a Y-axis value)that define a location of each corner of the blob. The parking metadatamay further include a timestamp (e.g., a date and time the image wasrecorded), a camera identifier (e.g., identifying the camera 116), alocation identifier (e.g., identifying the camera node 106 or a locationof the camera node 106), and a blob identifier (e.g., a uniqueidentifier assigned to the vehicle 122). As an example, the blob shownin the image may correspond to the vehicle 122, though application ofthe methodologies described herein is not necessarily limited tovehicles, and may find application in other contexts such withmonitoring trash or other parking obstructions.

At operation 610, the occupancy engine 310 determines an occupancystatus of the parking space 120 shown in the image based on the pixelcoordinates of the blob (e.g., vehicle 122) included in the metadata ofthe image. The occupancy status of a parking space indicates whether avehicle is parked in the parking space 120. Accordingly, in determiningthe occupancy status of the parking space 120, the occupancy engine 310determines whether the vehicle 122 is parked in the parking space. Theoccupancy engine 310 may determine the occupancy status of the parkingspace 120 based on a comparison of the real-world location of the blob(e.g., vehicle 122) to a known location (e.g., in the real-world) of theparking space 120 (e.g., accessed from a location look-up table accessedfrom the data store 318). The location of the blob (e.g., vehicle 122)may be derived from the pixel coordinates and a known location of thecamera node 106. Further details of the process for determiningoccupancy of parking spaces are discussed below in reference to FIGS.8-11, according to some embodiments.

At operation 615, the occupancy engine 310 updates one or more dataobject (e.g., maintained in the data store 318) to reflect the occupancystatus of the parking space 120. In some embodiments, the updating ofthe one or more data objects includes updating a field in a data objectcorresponding to the parking space 120 to reflect that the parking space120 is either occupied (e.g., a vehicle is parked in the parking space120) or unoccupied (e.g., a vehicle is not parked in the parking space120). In some embodiments, the updating of the one or more data objectsincludes: updating a first field in a data object corresponding to thevehicle 122 to include an indication of whether the vehicle 122 isparked or in motion; and updating a second field in the data objectcorresponding to the vehicle 122 to include the location of the vehicle122 at a time corresponding to a timestamp of the image (e.g., includedin the metadata of the image).

In response to the occupancy engine 310 determining the vehicle 122 isparked in the parking space 120, the rules violation engine 308determines whether the vehicle 122 is in violation of a parking ruleincluded in a parking policy associated with (e.g., applicable to) theparking space 120, at decision block 620. In determining whether thevehicle 122 is in violation of a parking policy, the parking engineaccesses a data object (e.g., a table) from the data store 318 thatincludes a parking policy applicable to the parking space 120. Theparking policy may include one or more parking rules that impose aconstraint (e.g., a time limit) on parking in the parking space 120.Certain parking rules may be associated with certain times or dates.Accordingly, the determining of whether the vehicle 122 is in violationof a parking rule includes determining which parking rules of theparking policy are applicable to the vehicle 122, which, may, in someinstances, be based on the timestamp of the image (e.g., included in theparking metadata).

In instances in which an applicable parking rule includes a time limiton parking in the parking space 120, the rules violation engine 308 maymonitor the parking metadata received from the camera 116 showing theparking space 120 and the vehicle 120 to determine an elapsed timeassociated with the occupancy of the parking space 120 by the vehicle122. The rules violation engine 308 may determine the elapsed time ofthe occupancy of the parking space 120 based on a comparison of a firsttimestamp included in parking metadata from which vehicle 122 wasdetermined to be parked in the parking space 120, and a second timestampincluded in the metadata being analyzed. Once the rules violation engine308 determines the elapsed time associated with the occupancy of theparking space 120, the parking rules engine 308 determines whether theelapsed time exceeds the time limit imposed by the parking rule.

If, at decision block 620, the parking rules engine 316 determines thevehicle 122 is in violation of a parking rule included in the parkingpolicy associated with the parking space 120, the method continues tooperation 625 where the parking rules engine 316 updates a data object(e.g., stored and maintained in the data store 318) associated with thevehicle 122 to reflect the parking rule violation. The updating of thedata object may include augmenting the data object to include anindication of the parking rule violation (e.g., setting a flagcorresponding to a parking rule violation). The updating of the dataobject may further include augmenting the data object to include anidentifier of the parking rule being violated.

At operation 630, the interface module 300 generates presentation datarepresenting a UI (e.g., a parking attendant interface) for monitoringparking space occupancy and parking rules violations in a parking areathat includes the parking space 120. The presentation data may includeimages a geospatial map of the area surrounding the parking space 120,visual indicators of parking space occupancy (e.g., based on informationincluded in data objects associated with the parking spaces), visualindicators of parking rule violations (e.g., based on informationincluded in data objects associated with the parking spaces),identifiers of specific parking rules being violated, images of thevehicle 122, and textual information describing the vehicle (e.g., make,model, color, and license plate number). Accordingly, in generating thepresentation data, the parking policy management system 102 mayretrieve, from the camera node 106, a first image corresponding to afirst timestamp included in parking metadata from which vehicle 122 wasdetermined to be parked in the parking space 120, and a second imagecorresponding to the parking metadata from which the parking monitoring102 determined that the vehicle 122 is in violation of the parking rule.

At operation 635, the interface module 300 causes presentation of the UIon the client device 106. In causing presentation of the UI, theinterface module 300 may transmit presentation data to the client device104 to cause the client device 104 to present the UI on a display of theclient device 104. Upon receiving the presentation data, the clientdevice 104 may temporarily store the presentation data to enable theclient device to display the UI.

The UI may include the geospatial map overlaid with visual indicators ofparking space occupancy and parking rule violations that may beselectable (e.g., through appropriate user input device interaction withthe UI) to presented additional UI elements that include the images ofthe vehicle 122, and textual information describing the vehicle. Furtherdetails of example interfaces provided by the parking policy managementsystem 102 are discussed below in reference to FIGS. 13-17, according tosome embodiments.

In some instances, multiple camera nodes may record an image of the sameview (e.g., images of the same vehicle and parking space) and send theparking metadata for these images to the parking policy managementsystem 102. In these instances, the parking policy management system 102may identify and select a single image for processing to reduce thenumber of calculations performed in furtherance of processing parkingspace occupancy and parking rule violations. Accordingly, as shown inFIG. 7, the method 600 may include the additional operations 705, 710,715, 720, and 725, which relate to selecting a single image frommultiple images showing the parking space 120. In some exampleembodiments, operations 705, 710, 715, 720, and 725 included in themethod 600 may be performed prior to or as part (e.g., a precursor task,a subroutine, or a portion) of operation 605 of method 600, in which theoccupancy engine 310 accesses parking metadata data describing an imageshowing the parking space 120 and the vehicle 122.

At operation 705, the data intake module 302 receives metadataassociated with multiple images. The metadata for each image includes aset of pixel coordinates (e.g., a coordinate pair defining a location ofeach corner) corresponding to a blob (e.g., a polygon) shown in theimage, a timestamp (e.g., a date and time the image was recorded), acamera identifier (e.g., identifying the camera 116), a locationidentifier (e.g., identifying the camera node 106 or a location of thecamera node 106), and a blob identifier (e.g., a unique identifierassigned to the vehicle 122).

At operation 710, the data intake module 302 determines, based on themetadata, that each of the multiple image show at least a portion of thesame view. For example, multiple instances of the camera node 106 may bepositioned such that multiple images of the parking space 120 arerecorded, albeit from different perspectives. The data intake module 302may determine that each of the multiple images shows at least a portionof the same view based on known locations (e.g., accessed from a tablemaintained in the data store 318) of the camera node 106 or cameras 116identified in the metadata.

At operation 715, the data intake module 302 determines a weighted valuefor each images based on respective metadata for the image. The weightedvalue is used to determine which image of the multiple images to processto monitor parking space occupancy and parking policy violation for theparking space 122 shown in each of the images. The data intake module302 may use various different parameters to determine the image to beprocessed. For example, the data intake module 302 may considerparameters such as percent of vehicle overlap with the parking space(e.g., as determined based on a comparison of derived locations of thevehicle 122 and known locations of the parking space 120), imagetimestamp, image quality, camera type, and confidence level or otherstatistics for a given camera. The data intake module 302 may assign avalue to each parameter (e.g., based on information included in alook-up table stored in the data store 318), and aggregate (e.g., sum oraverage) assigned parameter values to produce the weighted value.

At operation 720, the data intake module 302 selects a single image fromthe multiple images for processing (e.g., monitoring parking spaceoccupancy and determining parking policy violations) based on theweighted value. The data intake module 302 may, for example, rank theimages according to the weighted value, and select the highest rankedimage (e.g., the image with the greatest weighted value).

At operation 725, the data intake module 302 persists the metadata datafrom the selected image to the data store 318. In persisting the parkingmetadata to the database, the data intake module 302 may create ormodify a data object associated with the camera node 106 or the parkingspace 120. The created or modified data object includes the metadata ofthe selected image. The data intake module 302 may store subsequentparking metadata received from the camera node 106 from which theselected image was recorded while disregarding the metadata produced foreach of the other instances of camera nodes 106. The data intake module302 may store such metadata in the same data object or in another dataobject that is linked to that data object. In this way, the parkingpolicy management system 102 maintains a log of parking activity withrespect to the parking space 120.

FIG. 8 is a flowchart illustrating a method 800 for determiningoccupancy of a parking space by a vehicle, according to someembodiments. The method 800 may be embodied in computer-readableinstructions for execution by one or more processors such that theoperations of the method 800 may be performed in part or in whole by theparking policy management system 102; accordingly, the method 800 isdescribed below by way of example with reference thereto. However, itshall be appreciated that at least some of the operations of the method400 may be deployed on various other hardware configurations and themethod 800 is not intended to be limited to the parking managementsystem 102. In some example embodiments, the method 800 may be performedas part (e.g., a precursor task, a subroutine, or a portion) ofoperation 410 of method 400, in which the occupancy engine 310determines the occupancy status of the parking space 120. Morespecifically, the method 800 may be performed as part of determiningwhether the vehicle 122 is parked in the parking space 120.

At operation 805, the overlap module 312 determines the vehicle 122overlaps the parking space 120. More specifically, the overlap module312 determines a location of the vehicle 122 (e.g., derived from thepixel coordinates of the vehicle 122) overlaps a known location of theparking space 120 (e.g., access from the data store 318). In someembodiments, the overlap module 312 converts the pixel coordinates ofthe vehicle 122 (e.g., coordinates of the vehicle in the image space) toglobal coordinates (e.g., real-world geospatial coordinates). Furtherdetails regarding the determination of the overlap of the vehicle 122with the parking space 120 are discussed below in reference to FIG. 9and FIG. 10, according to some embodiments.

At operation 810, the motion module 314 determines the vehicle 122 isstationary. The determination of whether the vehicle 122 is stationarymay include comparing a first set of coordinates of the vehicle 122 at afirst time (e.g., a first timestamp included in metadata with the firstset of coordinates) to a second set of coordinates of the vehicle 122 ata second time (e.g., a second timestamp included in metadata with thesecond set of coordinates). Further details regarding the determinationof whether the vehicle 122 is stationary or is in motion are discussedbelow in reference to FIG. 9.

FIG. 9 is a flowchart illustrating a method 900 for determining whethera vehicle overlaps a parking space, according to some embodiments. Themethod 900 may be embodied in computer-readable instructions forexecution by one or more processors such that the operations of themethod 900 may be performed in part or in whole by the parking policymanagement system 102; accordingly, the method 900 is described below byway of example with reference thereto. However, it shall be appreciatedthat at least some of the operations of the method 900 may be deployedon various other hardware configurations and the method 900 is notintended to be limited to the parking management system 102. In someexample embodiments, the method 900 may be performed as part (e.g., aprecursor task, a subroutine, or a portion) of operation 605 of method600, in which the overlap module 312 determines the vehicle 122 isoverlapping the parking space 120.

At operation 905, the overlap module 312 accesses a set of pixelcoordinates of the vehicle 122. The pixel coordinates of the vehicle 122specify a location of the vehicle within an image recorded by the camera116 of the camera node 106. The set of pixel coordinates are included inmetadata of the image, and are provided by the camera node 106. The setof pixel coordinates may include a coordinate pair (e.g., an X-axiscoordinate and a Y-axis coordinate) of each corner of the vehicle (e.g.,an intersection point of each linear segment defining the border of thevehicle).

At operation 910, the overlap module 312 translates the set of pixelcoordinates of the vehicle to a set of global coordinates (e.g.,coordinates within a geographic coordinate system). As with the set ofpixel coordinates, the set of global coordinates may include acoordinate pair (e.g., longitude and latitude) of each corner of thevehicle. The set of global coordinates specify the geographic (e.g.,real-world) location of the vehicle 122. The overlap module 312 may, forexample, use a homography matrix algorithm to perform a direct lineartransformation of the set of pixel coordinates from camera node 106 tothe set of global coordinates (e.g., geospatial coordinates). Theoverlap module 312 may persist (e.g., store) the translated set ofglobal coordinates of the vehicle 122 in a data object associated withthe vehicle 122 for use in further processing, as needed.

At operation 915, the overlap module 312 accesses a set of known globalcoordinates (e.g., geospatial coordinates) of the parking space 120. Theoverlap module 312 may access the set of known global coordinates of theparking space from a table (e.g., stored in the data store 318) thatincludes a set of known coordinates for multiple parking spaces. Theoverlap module 312 may identify the global coordinates of the parkingspace 120 using any combination of location identifier, cameraidentifier, or parking space identifier included in the parkingmetadata. The set of global coordinates include specify the geospatial(e.g., real-world) location of each corner of the parking space 120.

At operation 920, the overlap module 312 compares the set of globalcoordinates of the vehicle 122 to the set of known global coordinates ofthe parking space 120 to determine an overlap amount of the vehicle 122with respect to the parking space 120. The overlap amount specifies anamount of the vehicle 122 that covers the parking space 120. In someexamples, the overlap amount corresponds to a percentage (e.g., thevehicle 122 overlaps 80% of the parking space 120). The overlap module312 may determine the overlap amount by calculating a distance betweenlocations defined by the set of global coordinates of the vehicle 122 tothe set of known global coordinates of the parking space 120.

In some embodiments, the overlap module 312 may determine the overlapamount by computing a first centroid using the set of global coordinatesof the vehicle 122 and a second centroid using the set of known globalcoordinates of the parking space 120. The overlap module 312 may thencompare the first and second centroid to determine the distance betweenthe first and second centroid. In this example, the distance between thefirst and second centroid (e.g., the distance between the first andsecond centroid) corresponds to the overlap amount.

At operation 925, the overlap module 312 determines whether the overlapamount transgresses a configurable threshold overlap amount. Thethreshold overlap may be a default value set by an administrator of theparking monitor system 102, or may be received from the client device104 (e.g., as a submission from the user 110 or a preference of the user110). The threshold overlap amount may be a minimum overlap amount.Thus, an overlap amount may be considered as transgressing the thresholdoverlap as a result of the overlap amount being higher than the minimumoverlap amount.

If the overlap module 312 determines the overlap amount transgresses theconfigurable threshold overlap amount, the overlap module 312 determinesthe vehicle 122 overlaps the parking space 120, at operation 930. If theoverlap module 312 determines the overlap amount fails to transgress theconfigurable threshold overlap, the overlap module 312 determines theparking space 120 is unoccupied, at operation 935.

At operation 940, the overlap module 312 updates one or more dataobjects to reflect the result of the determination made at decisionblock 925. For example, upon determining the overlap amount transgressesthe threshold overlap amount, the overlap module 312 may update a dataobject associated with the parking space 120 (e.g., the parking zonedata object 400) to reflect the overlap by the vehicle 122 (e.g., bysetting or clearing a flag). The overlap module 312 may further update adata object associated with the vehicle 122 (e.g., a vehicle dataobject) to reflect that the vehicle 122 is overlapping the parking space120 (e.g., by setting or clearing a flag). Upon determining that thevehicle 122 does not transgress the threshold overlap amount, theoverlap module 312 may update a data object associated with the parkingspace 120 (e.g., the parking zone data object 400) to reflect that theparking space is unoccupied (e.g., by setting or clearing a flag).

FIG. 10 is a flowchart illustrating a method for determining whether avehicle overlaps a parking space, according to some alternativeembodiments. The method 1000 may be embodied in computer-readableinstructions for execution by one or more processors such that theoperations of the method 1000 may be performed in part or in whole bythe parking policy management system 102; accordingly, the method 1000is described below by way of example with reference thereto. However, itshall be appreciated that at least some of the operations of the method1000 may be deployed on various other hardware configurations and themethod 1000 is not intended to be limited to the parking managementsystem 102. In some example embodiments, the method 1000 may beperformed as part (e.g., a precursor task, a subroutine, or a portion)of operation 605 of method 600, in which the overlap module 312determines the vehicle 122 is overlapping the parking space 120.

At operation 1005, the overlap module 312 accesses a set of pixelcoordinates of the vehicle 122. The pixel coordinates of the vehicle 122specify a location of the vehicle within an image recorded by the camera116 of the camera node 106. The set of pixel coordinates are included inmetadata of the image, and are provided by the camera node 106. The setof pixel coordinates may include a coordinate pair (e.g., an X-axiscoordinate and a Y-axis coordinate) of each corner of the vehicle (e.g.,an intersection point of each linear segment defining the border of thevehicle).

At operation 1010, the overlap module 312 module computes a centroid(e.g., the geometric center) of the vehicle 122 using a set ofcoordinates of the vehicle 122. The overlap module 312 may compute thecentroid of the vehicle 122 (also referred to herein as a “vehiclecentroid”) by calculating the arithmetic mean position of all points(e.g., corners) in the vehicle 122 defined by the set of coordinates. Insome embodiments, the overlap module 312 computes the centroid of thevehicle 122 using the set of pixel coordinates of the vehicle 122.

In other embodiments, the overlap module 312 computes the centroid ofthe vehicle 122 using a set of global coordinates of the vehicle 122.Accordingly, the computing of the vehicle centroid may includetranslating the set of pixel coordinates of the vehicle 122 to a set ofglobal coordinates (e.g., coordinates within a geographic coordinatesystem). The overlap module 312 may, for example, use a homographymatrix algorithm to perform a direct linear transformation of the set ofpixel coordinates from camera node 106 to the set of global coordinates(e.g., geospatial coordinates).

At operation 1015, the overlap module 312 module computes a centroid(e.g., the geometric center) of the parking space 120 using a set ofcoordinates of the parking space 120. The overlap module 312 may computethe centroid of the parking space 120 (also referred to herein as a“parking space centroid”) by calculating the arithmetic mean position ofall points in the vehicle 122 defined by the set of coordinates.Depending on the embodiment, the overlap module 312 may computes theparking space centroid using either a set of known pixel coordinates(e.g., coordinates within the image space) of the parking space 120 or aset of known global coordinates (e.g., geospatial coordinates) of theparking space 120. Accordingly, in computing the parking space centroid,the overlap module 312 accesses either a set of known pixel coordinatesor a set of known global coordinates (e.g., geospatial coordinates) ofthe parking space 120. The overlap module 312 may access either the setof coordinates (e.g., global or pixel) of the parking space 120 from atable (e.g., stored in the data store 318) that includes a set of knowncoordinates for multiple parking spaces. The overlap module 312 mayidentify the coordinates of the parking space 120 using any combinationof location identifier, camera identifier, or parking space identifierincluded in the parking metadata.

At operation 1020, the overlap module 312 compares the vehicle centroidto the parking space centroid to determine an overlap amount of thevehicle 122 with respect to the parking space 120. The overlap amountspecifies an amount of the parking space 120 covered by the vehicle 122.The overlap module 312 may determine the overlap amount by calculating adistance (e.g., a difference in position) between the vehicle centroidand the parking space centroid.

At operation 1025, the overlap module 312 determines whether the overlapamount transgresses a configurable threshold overlap amount. Thethreshold overlap may be a default value set by an administrator of theparking monitor system 102, or may be received from the client device104 (e.g., as a submission from the user 110 or a preference of the user110). The threshold overlap amount may be a minimum overlap amount.Thus, an overlap amount may be considered as transgressing the thresholdoverlap as a result of the overlap amount being higher than the minimumoverlap amount.

If the overlap module 312 determines the overlap amount transgresses theconfigurable threshold overlap amount, the overlap module 312 determinesthe vehicle 122 overlaps the parking space 120, at operation 1030. Ifthe overlap module 312 determines the overlap amount fails to transgressthe configurable threshold overlap, the overlap module 312 determinesthe parking space 120 is unoccupied, at operation 1035.

At operation 1040, the overlap module 312 updates one or more dataobjects to reflect the result of the determination made at decisionblock 1025. For example, upon determining the overlap amounttransgresses the threshold overlap amount, the overlap module 312 mayupdate a data object associated with the parking space 120 (e.g., theparking zone data object 400) to reflect the overlap by the vehicle 122(e.g., by setting or clearing a flag). The overlap module 312 mayfurther update a data object associated with the vehicle 122 (e.g., avehicle data object) to reflect that the vehicle 122 is overlapping theparking space 120 (e.g., by setting or clearing a flag). Upondetermining that the vehicle 122 does not transgress the thresholdoverlap amount, the overlap module 312 may update a data objectassociated with the parking space 120 (e.g., the parking zone dataobject 400) to reflect that the parking space is unoccupied (e.g., bysetting or clearing a flag).

FIG. 11 is a flowchart illustrating a method for determining whether avehicle is stationary or in motion, according to some embodiments. Themethod 1100 may be embodied in computer-readable instructions forexecution by one or more processors such that the operations of themethod 1100 may be performed in part or in whole by the parking policymanagement system 102; accordingly, the method 1100 is described belowby way of example with reference thereto. However, it shall beappreciated that at least some of the operations of the method 1100 maybe deployed on various other hardware configurations and the method 1100is not intended to be limited to the parking management system 102. Insome example embodiments, the method 1100 may be performed as part(e.g., a precursor task, a subroutine, or a portion) of operation 610 ofmethod 600, in which the motion module 314 determines the vehicle 122 isstationary. In other example embodiments, the method 1100 may beperformed as part of a method for tracking moving vehicles, details ofwhich are discussed below in reference to FIG. 12.

At operation 1105, the motion module 314 accesses a first set of pixelcoordinates of the vehicle 122 at a first time. The first pixelcoordinates of the vehicle 122 specify a location of the vehicle withina first image recorded by the camera 116 of the camera node 106. Thefirst set of pixel coordinates are included in metadata of the firstimage, and are provided by the camera node 106. The metadata of thefirst image include a first timestamp corresponding to the first time.

At operation 1110, the motion module 314 accesses a second set of pixelcoordinates of the vehicle 122 at a second time that is subsequent tothe first time. The second pixel coordinates of the vehicle 122 specifya location of the vehicle within a second image recorded by the camera116 of the camera node 106. The second set of pixel coordinates areincluded in metadata of the second image, and are provided by the cameranode 106. The metadata of the second image include a second timestampcorresponding to the second time.

At operation 1115, the motion module 314 module computes a firstcentroid (e.g., the geometric center) of the vehicle 122 at the firsttime using the first set of pixel coordinates. The motion module 314 maycompute the first vehicle centroid by calculating the arithmetic meanposition of all points in the vehicle 122 defined by the first set ofpixel coordinates.

At operation 1120, the motion module 314 module computes a secondcentroid (e.g., the geometric center) of the vehicle 122 at the secondtime using the second set of pixel coordinates. The motion module 314may compute the second vehicle centroid by calculating the arithmeticmean position of all points in the vehicle 122 defined by the first setof pixel coordinates.

In some embodiments, the motion module 314 computes the first and secondvehicle centroid using a first and second set of global coordinates ofthe vehicle 122. Accordingly, the computing of the first and secondvehicle centroids may include translating the first and second set ofpixel coordinates of the vehicle 122 to a first and second set of globalcoordinates (e.g., coordinates within a geographic coordinate system).The motion module 314 may, for example, use a homography matrixalgorithm to perform a direct linear transformation of the sets of pixelcoordinates from camera node 106 to the sets of global coordinates(e.g., geospatial coordinates).

At operation 1125, the motion module 314 compares first vehicle centroidto the second vehicle centroid to determine a change in position (e.g.,a distance) of the vehicle 122 between the first time and the secondtime. The position change includes a difference in location (e.g.,measured using a distance metric such as feet or meters) of the vehicle122 between the first time and the second time.

At operation 1130, the motion module 314 determines whether the changein position transgresses a configurable threshold position change. Thethreshold position change may be a default value set by an administratorof the parking monitor system 102, or may be received from the clientdevice 104 (e.g., as a submission from the user 110 or a preference ofthe user 110). The threshold position change may be a maximum allowableposition change. Thus, a position change may be considered astransgressing the threshold position change as a result of the positionchange being higher than the maximum allowable position change.

If the motion module 314 determines the position change transgresses theconfigurable threshold position change (e.g., the position change isgreater than the maximum allowable position change), the motion module314 determines the vehicle 122 is in motion, at operation 1135. Upondetermining the vehicle 122 is in motion, the motion module 314 updatesa data object (e.g. stored in the data store 318) associated with thevehicle 122 to indicate that the vehicle 122 is in motion, and themotion module 314 tags the vehicle 122 for further monitoring. Furtherdetails regarding the monitoring and tracking of moving vehicles arediscussed below in reference to FIG. 10.

If the motion module 314 determines the position changes fails totransgress the configurable threshold positions change, the methodproceeds to decision block 1140 where the motion module 314 determineswhether a time difference between the first time and the second timetransgressing a configurable threshold time difference. The thresholdtime difference may be a default value set by an administrator of theparking monitor system 102, or may be received from the client device104 (e.g., as a submission from the user 110 or a preference of the user110). The threshold time difference may be a maximum allowable timedifference or a minimum allowable time difference. Thus, a timedifference may be considered as transgressing the threshold timedifference as a result of the time change being higher than a maximumallowable time.

If the motion module 314 determines the time difference transgresses theconfigurable threshold time difference, the method 1100 returns tooperation 1135 where the motion module 314 determines the vehicle 122 isin motion. If the motion module 314 determines the time difference failsto transgress the configurable threshold time difference (e.g., the timedifference is lower than a maximum allowable time difference, or thetime difference is higher than a minimum allowable time difference), themotion module 314 determines the vehicle 122 is stationary.

FIG. 12 is a flowchart illustrating a method 1200 for tracking a movingvehicle (e.g., vehicle 122), according to some embodiments. The method1200 may be embodied in computer-readable instructions for execution byone or more processors such that the operations of the method 1200 maybe performed in part or in whole by the parking policy management system122; accordingly, the method 1200 is described below by way of examplewith reference thereto. However, it shall be appreciated that at leastsome of the operations of the method 1200 may be deployed on variousother hardware configurations and the method 1200 is not intended to belimited to the parking management system 122.

At operation 1205, the coordinate translation module 308 receivesmetadata associated with multiple images recorded by multiple cameranodes (e.g., multiple instances of camera node 126). The metadataincludes at least a first set of pixel coordinates (e.g., one or morecoordinate pairs defining a location of each corner) corresponding to afirst blob (e.g., a polygon) shown in a first image recorded by a firstcamera and a second set of pixel coordinates (e.g., one or morecoordinate pairs defining a location of each corner) corresponding to asecond blob (e.g., a polygon) shown in a second image recorded by asecond camera. The metadata for each image may further include atimestamp (e.g., a date and time the image was recorded), a cameraidentifier (e.g., identifying the camera 116), a location identifier(e.g., identifying the camera node 126 or a location of the camera node126), and a blob identifier (e.g., a unique identifier assigned to thevehicle 122).

At operation 1210, the coordinate translation module 308 translates thefirst and second set of pixel coordinates to a first and second set ofglobal coordinates (e.g., geospatial coordinates), respectively. The setof global coordinates may include a coordinate pair (e.g., longitude andlatitude) that define a geospatial location of each corner of the blob.The coordinate translation module 308 may, for example, use a homographymatrix algorithm to perform a direct linear transformation of the set ofpixel coordinates to the set of global coordinates (e.g., geospatialcoordinates).

At operation 1215, the unique vehicle identification module 306determines the vehicle 122 is shown in the first and second image basedin part on the first and second set of global coordinates. In otherwords, the unique vehicle identification module 306 determines that thefirst blob shown in the first image is the same as the second blob shownin the second image, and that both of which correspond to the samevehicle—vehicle 122.

In determining the vehicle 122 is shown in both images, the uniquevehicle identification module 306 access known information (e.g., fromthe data store 318) about the physical orientation of the first andsecond camera (e.g., angle, height, and position) using the uniquecamera identifiers included in the metadata of the images. Using theknown information about the physical orientation of the first and secondcamera such as angle, height, and position, the unique vehicleidentification module 306 compares the first and second set of globalcoordinates to determine if the difference in location represented bythe difference between the two set of global coordinates is below anallowable threshold. The allowable threshold may, for example, be basedon an expected trajectory of a vehicle in the area of the first andsecond camera based on speed limits, traffic conditions, and other suchfactors. Based on the difference in location represented by thedifference between the two sets of global coordinates being below theallowable threshold, the unique vehicle identification module 306determines the vehicle shown in the first image is also the vehicleshown in the second image.

At operation 1220, the motion module 314 determines the vehicle 122,which is shown in both the first and second images, is in motion. Thedetermination that the vehicle 122 is in motion may include computing afirst centroid for the first set of global coordinates, and computing asecond centroid for the second set of global coordinates. The motionmodule 314 may further compare the first and second centroid todetermine whether the position change represented by the differencebetween the first and second centroids transgresses a threshold positionchange. Further details regarding the determination of a vehicle beingin motion are discussed above with respect to FIG. 9, according to someembodiments.

Based on determining the vehicle 122 is in motion, the motion module 314updates a data object (e.g., stored in the data store 318) associatedwith the vehicle 122 to include location information, at 1225. Thelocation information includes the geospatial locations defined by thefirst and second set of global coordinates. In this way, the motionmodule 314 may track and maintain a record of a path of a movingvehicle.

At operation 1230, the interface module 300 generates presentation datarepresenting a UI (e.g., a parking attendant interface) for monitoringand tracking movement of vehicles. The presentation data may includeimages a geospatial map of an area (e.g., a municipality), visualindicators of the path of moving vehicles that may include flags orother indicators of particular waypoints in the paths (e.g.,corresponding to global coordinates derived from pixel coordinatesprovided by one or more camera nodes 126), and textual informationdescribing the moving vehicles (e.g., make, model, color, and licenseplate number). Accordingly, in generating the presentation data, theparking policy management system 122 may retrieve, from the data store318, the location information of the vehicle 122 that includes the firstand second set of global coordinates. The interface module 300 thenplots visual indicators (e.g., icons) of the first and second sets ofglobal coordinates on the geospatial map.

At operation 1235, the interface module 300 causes presentation of theUI on a client device in communication with the parking policymanagement system 122 (e.g., the client device 124). In causingpresentation of the UI, the interface module 300 may transmitpresentation data to the client device 104 to cause the client device104 to present the UI on a display of the client device 104. Uponreceiving the presentation data, the client device 104 may temporarilystore the presentation data to enable the client device to display theUI.

The UI may include the geospatial map overlaid with visual indicators ofthe path of moving vehicles that may include flags or other indicatorsof particular waypoints in the paths (e.g., corresponding to globalcoordinates derived from pixel coordinates provided by one or morecamera nodes 126). In other words, the UI includes a geospatial map withplots of determined locations of the vehicle 122. The visual indicatorsmay be selectable (e.g., through appropriate user input deviceinteraction with the UI) to presented additional UI elements thatinclude images of the vehicle 122, and textual information describingthe vehicle.

It shall be appreciated that the operations of the method 1200 may berepeated for any number of subsequent images (e.g., a third image,fourth image, etc.) in which the unique vehicle identification module304 may identify the vehicle 122. In this way, while in motion, thevehicle 122 may be identified from metadata for multiple images, and thelocations visited or passed by the moving vehicle may continue to betracked and presented on the geospatial map of the UI.

FIGS. 13A-13E are interface diagrams illustrating portions of an exampleUI 1300 for creating or modifying a parking zone, according to someembodiments. The UI 1300 may, for example, be presented on the clientdevice 106, and may enable a parking policy administrator (or otherparking policy enforcement management or administrative personnel) tocreating parking zones. As shown in FIG. 13A, the UI 1300 initiallyincludes a geospatial map 1302 of a given area (e.g., a municipality).The geospatial map 1302 may be configured to receive user inputspecifying a location of a parking zone. For example, the user 110 mayuse an input device (e.g., mouse or touch screen) to trace an outline ofthe location of the parking zone on the geospatial 1302.

The UI 1300 also includes a pane 1304 from which the user 110 mayselect: button 1306 to create a new parking zone (e.g., by tracing anoutline of the location of the parking zone on the geospatial map 1302);button 1308 to clone (e.g., duplicate) an existing parking zone; orbutton 1310 to modify an existing parking zone. Information describingexisting parking zone is maintained in respective parking zone dataobject stored in the data store 318.

As an example of the operability of the buttons included in the pane1302, FIG. 13B illustrates a window 1312 that may be presented inresponse to receiving a user selection (e.g., user 110) of the button1310, according to some embodiments. As shown, the window 1312 isdisplayed overlaid on the geospatial map 1302 and pane 1304. The window1312 includes a list of existing parking zone identified by parking zoneidentifier (e.g., automatically assigned to the parking zone by theparking policy creation module 304 upon generating the correspondingparking zone data object), address, and city. The user 110 may selectone of the parking zones from the list, for example, by clicking on theparking zone and clicking on button 1314.

For example, upon receiving selection of parking zone 1316, the parkingmanagement system 102 access a parking zone data object for the parkingzone 1314 (e.g., parking zone data object 400), and the interface module300 may update the UI 1300 to include additional information about theparking zone 1316, as illustrated in FIG. 13C. More specifically, asillustrated in FIG. 13C, the pane 1304 has been updated to includemultiple tabs (e.g., tabs 1318, 1320, 1322, and 1324) that, whenselected through appropriate user interaction (e.g., by clicking on thetab), display detailed information about particular aspects of theparking zone 1314. In particular, tab 1318 includes a number of fieldsfor receiving a presenting general information about the parking zone1316 such as address, city, state, zip code, location type, zone type,time zone, and metered status. The geospatial map 1302 is also updatedto include a graphical representation of the parking zone 1316 overlaidon the geospatial map 1302.

The user 110 may select tab 1320 to view detailed location informationfor the parking zone. For example, FIG. 13D illustrates an update to thepane 1304 by the interface module 300 in response to selection of thetab 1320. As shown, the tab 1320 of the pane 1304 includes apresentation of a set of global coordinates (e.g., geospatialcoordinates) of a parking space within the parking zone 1316. The set ofglobal coordinates include a coordinate pair (e.g., a latitude value anda longitude value) for each corner of the parking space. Further, eachcoordinate pair (e.g., each corner of the parking space) is plotted onthe geospatial map 1302 (points 1326-1329) so as to display the locationof the parking space as defined by the set of global coordinates. Theuser 110 may edit the location of the parking space by either manuallychanging the coordinates displayed in the pane 1304 or by dragging anddropping any one of the points 1326-1329 through appropriate interactionwith the UI 1300 with an input device.

As illustrated in FIG. 13E, the user 110 may select tab 1322 to view oredit a parking policy associated with the parking zone 1316. As shown,the pane 1304 has been updated (e.g., by the interface module 300) inresponse to user selection of the tab 1322 to display a list of parkingrules comprising the parking policy associated with the parking zone1316. The user 110 may select individual rules to delete or to edit. Theuser 110 may further use calendar element 1330 to add or edit temporalattributes to any one of the displayed parking rules. The temporalattributes temporally limit the applicability of parking rules composingthe parking policy. For example, a temporal attribute may limit theapplicability of a parking rule to a particular time of day (e.g., 6AM-6 PM), a particular day of the week (e.g., Monday-Friday), or aparticular day of the year (e.g., holidays).

As illustrated in FIG. 13F, the user 110 may select tab 1324 to view oredit cameras associated with the parking zone 1316. As shown, the pane1304 has been updated (e.g., by the interface module 300) in response touser selection of the tab 1324 to display a list of cameras identifiersassociated with the parking zone 1316. As shown, the geospatial map 1302is updated (e.g., by the interface module 300) to include visualindicators of locations of the associated cameras.

Each of the cameras included in the list may record images showing atleast a portion of the parking zone 1316. Each camera may be identifiedby a unique camera identifier, and a camera node identifier (e.g., apole identifier) may be displayed in conjunction with each cameraidentifier. Each camera included in the list may also have an imagerecorded by the camera displayed in the pane 1304 along with the cameraidentifier.

For each camera identified in the list, the parking management system102 maintains a camera data object (e.g., storing information about thecamera) in association (e.g., electronically linked) with the parkingzone data object for the parking zone 1316 in the data store 318. Theuser 110 may add additional cameras through selection of button 1332,which causes the interface module 300 to prompt the user 110 to enter acamera identifier. Upon receiving the camera identifier, the parkingpolicy management system 102 associates the corresponding camera dataobject with the parking zone data object for the parking zone 1316.

FIGS. 14A-14D are interface diagrams illustrating portions of an exampleUI 1400 for monitoring parking rule violations in a parking zone,according to some embodiments. The UI 1400 may, for example, bepresented on the client device 106, and may enable a parking attendant(or other parking policy enforcement personnel) to monitor parkingpolicy violation in real-time. As shown, the UI 1300 includes ageospatial map 1402 of a particular area of a municipality. In someembodiments, the parking policy management system 102 may generate theUI 1300 to focus specifically of the area of the municipality assignedto the parking attendant user of the client device 102, while in otherembodiments the parking attendant user may interact with the UI 1400(e.g., through appropriate user input) to select and focus on the areato which they are assigned to monitor.

The UI 1400 further includes overview element 1404 that includes anoverview of the parking violations in the area. For example, theoverview element 1302 includes a total number of active violations and atotal number of completed violations (e.g., violations for which acitation has been given). The overview element 1404 also includesbreakdown of violations by priority (e.g., “High” “Medium” and “Low”).

The UI 1400 also includes indicators of locations parking ruleviolations. For example, the UI 1400 includes a pin 1406 that indicatesthat a vehicle is currently in violation of a parking rule at thelocation of the pin 1406. Each violation indicators may be adapted toinclude visual indicators (e.g., colors or shapes) of the priority ofthe parking rule violation (e.g., “High” “Medium” and “Low”).Additionally, the indicators may be selectable (e.g., throughappropriate user input by the user 130) to present further detailsregarding the parking rule being violated.

For example, upon receiving selection of the pin 1406, the userinterface module 300 updates the UI 1400 to include window 1408 forpresenting a description of the parking rule being violated, an addressof the location of the violation, a time period in which the vehicle hasbeen in violation, images 1410 and 1412 of the vehicle, and a distancefrom the current location of the parking attendant and the location ofthe parking rule violation (e.g., as determined by location informationreceived from the client device 106 and the set of global coordinatescorresponding to the determined parking policy violation). The window1408 also includes a button 1414 that when selected by the user 110causes the parking policy management system 102 to automatically issueand provide (e.g., mailed or electronically transmitted) a citation(e.g., a ticket) to an owner or responsible party of the correspondingvehicle.

Each of the images 1410 and 1412 include a timestamp corresponding tothe time at which the images were recorded. The image 1410 correspondsto the first image from which the parking policy management system 102determined the vehicle was parked in the parking space, and the image1412 corresponds to the first image from which the parking policymanagement system 102 determined the vehicle was in violation of theparking rule. As noted above, the parking policy management system 102determines that the vehicle is parked in the parking space and that thevehicle is in violation of the parking rule from the metadata describingthe images, rather than from the images themselves. Upon determining thevehicle is in violation of the parking rule, the parking policymanagement system 102 retrieves the images 1410 and 1412 from the cameranode that recorded the images (e.g., an instance of the camera node106).

The user 110 may select either image 1410 or 1412 (e.g., using a mouse)for a larger view of the image. For example, FIG. 14C illustrates alarger view of the image 1412 presented in response to selection of theimage 1412 from the window 1408. As shown, in the larger view, the image1410 includes a visual indicator (e.g., an outline) of the parking spacein which the vehicle is parked.

Returning to FIG. 14B, the user 110 may access a list view of theviolations through selection of icon 1416. As an example, FIG. 14Dillustrates a list view 1418 of violation in the area. As shown, theviolation is identified by location (e.g., address) and the list viewinclude further information regarding the parking rule being violation(e.g., “TIMEZONE VIOLATION”).

FIGS. 15A-15B are interface diagrams illustrating portions of an exampleUI 1500 for monitoring parking rule violations in a parking zone,according to some embodiments. The UI 1500 may, for example, bepresented on the client device 106, and may enable a parking attendant(or other parking policy enforcement personnel) to monitor parkingpolicy violation in real-time. As shown in FIG. 15A, the UI 1500includes a geospatial map 1502 of a particular area of a municipality.In some embodiments, the parking policy management system 102 maygenerate the UI 1500 to focus specifically of the area of themunicipality assigned to the parking attendant user of the client device102, while in other embodiments the parking attendant user may interactwith the UI 1500 (e.g., through appropriate user input) to select andfocus on the area to which they are assigned to monitor.

The UI 1500 further includes overview element 1504 that includes anoverview of the parking violations in the area. For example, theoverview element 1504 includes a cumulative total amount of currencycorresponding to monetary fines that may be imposed as a result of theparking rule violations in the area. The overview element 1504 alsoincludes a chart 1506 that shows a breakdown of the parking ruleviolations in the area according to duration of the violation.

The UI 1500 also includes a plurality of indicators of locations parkingrule violations. For example, the geospatial map 1502 includes a pin1508 that indicates that a vehicle is currently in violation of aparking rule at the location of the pin 1508. Each of the indicators maybe adapted to include visual indicators (e.g., colors or shapes) of aduration of the parking rule violation. Additionally, the indicators maybe selectable (e.g., through appropriate user input by the user 130) topresent further details regarding the parking rule being violated. Forexample, upon receiving selection of the pin 1508, the UI 1500 presentswindow 1510 that includes a description of the parking rule beingviolated, an amount of currency corresponding to a fine imposed forviolating the parking rule, and a distance from the current location ofthe parking attendant and the location of the parking rule violation(e.g., as determined by location information received from the clientdevice 106 and the set of global coordinates corresponding to thedetermined parking policy violation). The window 1510 also includes abutton 1512 that when selected by the user 110 causes the parking policymanagement system 102 to automatically issue and provide (e.g., mailedor electronically transmitted) a citation (e.g., a ticket) to an owneror responsible party of the corresponding vehicle. Additionally, thewindow 1510 includes a button 1514 that when selected by the user 110causes an additional window to be presented that includes additionaldetails about the vehicle and the parking rule violation.

For example, FIG. 15B is an interface diagram illustrating a violationdetail page 1550 that is presented as part of the UI 1500 in response touser selection of the button 1514. As shown, the violation detail page1550 includes images 1552 and 1554 of a vehicle parked in violation of aparking rule. Each of the images 1552 and 1554 include a timestampcorresponding to the time at which the images were recorded. The image1552 corresponds to the first image from which the parking policymanagement system 102 determined the vehicle was parked in the parkingspace, and the image 1554 corresponds to the first image from which theparking policy management system 102 determined the vehicle was inviolation of the parking rule. As noted above, the parking policymanagement system 102 determines that the vehicle is parked in theparking space and that the vehicle is in violation of the parking rulefrom the metadata describing the images, rather than from the imagesthemselves. Upon determining the vehicle is in violation of the parkingrule, the parking policy management system 102 retrieves the images 1552and 1554 from the camera node that recorded the images (e.g., aninstance of the camera node 106).

The violation detail page 1550 also includes an identifier of theparking rule (e.g., Municipal Code number) along with a description ofthe violation (e.g., “unlawful parking in disabled space”) and an amountof currency associated with a momentary fine imposed for violating theparking rule. The violation detail page 1400 further includesinformation about the vehicle such as a license plate number, a vehicletype, a driver address, and a number previous violations by a driver orowner of the vehicle. As shown, the information about the vehiclefurther includes an image 1556 of the license plate of the vehicle,which may also be provided by the camera node or specific camera thatrecorded the images 1552 and 1554.

FIG. 16 is an interface diagram illustrating an example UI 1600 formonitoring parking space occupancy in a parking zone, according to someembodiments. The UI 1600 may, for example, be presented on the clientdevice 106, and may enable a parking attendant (or other parking policyenforcement personnel) to monitor parking space occupancy in real-time.As shown in FIG. 16, the UI 1600 includes a geospatial map 1602 of aparticular area of a municipality (e.g., a particular parking zone). TheUI 1600 further includes filter pane 1602 that includes an overview ofthe parking space occupancy in the area and allows the user 110 tofilter displayed occupancy by time, type, and value. The filter pane1602 includes a cumulative total amount of currency corresponding tooccupancy of parking spaces generated through parking rule violationfines and parking fees. The filter pane 1602 also includes a chart 1606that shows a breakdown of the parking space occupancy by duration.

The UI 1600 also includes a plurality of indicators of parking spaceoccupancy throughout the area. For example, the geospatial map 1602includes an icon 1608 that provides information related to parkingoccupancy in the area near the location of the icon 1608 on thegeospatial map. Given that the “Value” filter is selected, the icon 1608displays an aggregate value of fines and fees received as a result ofoccupancy in the area of the icon 1608. It shall be appreciated that theicon 1608 may take different forms and may present different informationdepending on the filter selected from the filter pane 1602. For example,if the “Time” filter is selected, the geospatial map 1602 may include aplurality of occupancy indicators corresponding to occupied parkingspaces grouped according to the duration of time of the occupancy of thespace. As another example, if the “Type” filter is selected, thegeospatial map 1602 may include a plurality of occupancy indicatorscorresponding to occupied parking spaces grouped according to the typeof occupancy (e.g., “Illegal,” “Metered,” “Timed,” or “Permit”).

FIG. 17 is an interface diagram illustrating an example UI 1700 forpresenting an overview of parking information of a municipality,according to some embodiments. As shown, the UI 1700 includes a map ofan area (e.g., a municipality) along with a breakdown of informationabout parking in the area such as revenue generated by parking in thearea, utilization of parking in the area, and customer satisfaction withparking in the area. As shown, the breakdown of information is providedin various graphs and charts. The information displayed in the graphsand charts may be derived by the parking policy management system 102from the data objects (e.g., parking zone data objects, vehicle dataobjects, camera data objects, etc.) stored in the data store 318.

FIG. 18 is a block diagram illustrating components of a machine 1800,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 18 shows a diagrammatic representation of the machine1800 in the example form of a computer system, within which instructions1816 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 1800 to perform any oneor more of the methodologies discussed herein may be executed. Theseinstructions transform the general, non-programmed machine into aparticular machine programmed to carry out the described and illustratedfunctions of the system 1800 in the manner described herein. The machine1800 may operate as a standalone device or may be coupled (e.g.,networked) to other machines. In a networked deployment, the machine1800 may operate in the capacity of a server machine or a client machinein a server-client network environment, or as a peer machine in apeer-to-peer (or distributed) network environment. By way ofnon-limiting example, the machine 1800 may comprise or correspond to aserver computer, a client computer, a personal computer (PC), a tabletcomputer, a laptop computer, a netbook, a set-top box (STB), a personaldigital assistant (PDA), an entertainment media system, a cellulartelephone, a smart phone, a mobile device, a wearable device (e.g., asmart watch), a smart home device (e.g., a smart appliance), other smartdevices, a web appliance, a network router, a network switch, a networkbridge, or any machine capable of executing the instructions 1816,sequentially or otherwise, that specify actions to be taken by machine1800. Further, while only a single machine 1800 is illustrated, the term“machine” shall also be taken to include a collection of machines 1800that individually or jointly execute the instructions 1816 to performany one or more of the methodologies discussed herein.

The machine 1800 may include processors 1810, memory 1820, andinput/output (I/O) components 1850, which may be configured tocommunicate with each other such as via a bus 1802. In an exampleembodiment, the processors 1810 (e.g., a Central Processing Unit (CPU),a Reduced Instruction Set Computing (RISC) processor, a ComplexInstruction Set Computing (CISC) processor, a Graphics Processing Unit(GPU), a Digital Signal Processor (DSP), an Application SpecificIntegrated Circuit (ASIC), a Radio-Frequency Integrated Circuit (RFIC),another processor, or any suitable combination thereof) may include, forexample, processor 1812 and processor 1814 that may execute instructions1816. The term “processor” is intended to include multi-core processorthat may comprise two or more independent processors (sometimes referredto as “cores”) that may execute instructions contemporaneously. AlthoughFIG. 18 shows multiple processors, the machine 1800 may include a singleprocessor with a single core, a single processor with multiple cores(e.g., a multi-core process), multiple processors with a single core,multiple processors with multiples cores, or any combination thereof.

The memory/storage 1820 may include a memory 1822, such as a mainmemory, or other memory storage, and a storage unit 1826, bothaccessible to the processors 1810 such as via the bus 1802. The storageunit 1826 and memory 1822 store the instructions 1816 embodying any oneor more of the methodologies or functions described herein. Theinstructions 1816 may also reside, completely or partially, within thememory 1822, within the storage unit 1826, within at least one of theprocessors 1810 (e.g., within the processor's cache memory), or anysuitable combination thereof, during execution thereof by the machine1800. Accordingly, the memory 1822, the storage unit 1826, and thememory of processors 1810 are examples of machine-readable media.

As used herein, “machine-readable medium” means a device able to storeinstructions and data temporarily or permanently and may include, but isnot be limited to, random-access memory (RAM), read-only memory (ROM),buffer memory, flash memory, optical media, magnetic media, cachememory, other types of storage (e.g., Erasable Programmable Read-OnlyMemory (EEPROM)) and/or any suitable combination thereof. The term“machine-readable medium” should be taken to include a single medium ormultiple media (e.g., a centralized or distributed database, orassociated caches and servers) able to store instructions 1816. The term“machine-readable medium” shall also be taken to include any medium, orcombination of multiple media, that is capable of storing instructions(e.g., instructions 1816) for execution by a machine (e.g., machine1800), such that the instructions, when executed by one or moreprocessors of the machine 1800 (e.g., processors 1810), cause themachine 1800 to perform any one or more of the methodologies describedherein. Accordingly, a “machine-readable medium” refers to a singlestorage apparatus or device, as well as “cloud-based” storage systems orstorage networks that include multiple storage apparatus or devices. Theterm “machine-readable medium” excludes signals per se.

The I/O components 1850 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 1850 that are included in a particular machine will depend onthe type of machine. For example, portable machines such as mobilephones will likely include a touch input device or other such inputmechanisms, while a headless server machine will likely not include sucha touch input device. It will be appreciated that the I/O components1850 may include many other components that are not shown in FIG. 18.The I/O components 1850 are grouped according to functionality merelyfor simplifying the following discussion and the grouping is in no waylimiting. In various example embodiments, the I/O components 1850 mayinclude output components 1852 and input components 1854. The outputcomponents 1852 may include visual components (e.g., a display such as aplasma display panel (PDP), a light emitting diode (LED) display, aliquid crystal display (LCD), a projector, or a cathode ray tube (CRT)),acoustic components (e.g., speakers), haptic components (e.g., avibratory motor, resistance mechanisms), other signal generators, and soforth. The input components 1854 may include alphanumeric inputcomponents (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or other pointinginstrument), tactile input components (e.g., a physical button, a touchscreen that provides location and/or force of touches or touch gestures,or other tactile input components), audio input components (e.g., amicrophone), and the like.

In further example embodiments, the I/O components 1850 may includebiometric components 1856, motion components 1858, environmentalcomponents 1860, or position components 1862 among a wide array of othercomponents. For example, the biometric components 1856 may includecomponents to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram basedidentification), and the like. The motion components 1858 may includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environmental components 1860 may include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometer that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensors (e.g., gasdetection sensors to detection concentrations of hazardous gases forsafety or to measure pollutants in the atmosphere), or other componentsthat may provide indications, measurements, or signals corresponding toa surrounding physical environment. The position components 1862 mayinclude location sensor components (e.g., a Global Position System (GPS)receiver component), altitude sensor components (e.g., altimeters orbarometers that detect air pressure from which altitude may be derived),orientation sensor components (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 1850 may include communication components 1864operable to couple the machine 1800 to a network 1880 or devices 1870via coupling 1882 and coupling 1872, respectively. For example, thecommunication components 1864 may include a network interface componentor other suitable device to interface with the network 1880. In furtherexamples, communication components 1864 may include wired communicationcomponents, wireless communication components, cellular communicationcomponents, Near Field Communication (NFC) components, Bluetooth®components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and othercommunication components to provide communication via other modalities.The devices 1870 may be another machine or any of a wide variety ofperipheral devices (e.g., a peripheral device coupled via a UniversalSerial Bus (USB)).

Moreover, the communication components 1864 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 1864 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components1864, such as, location via Internet Protocol (IP) geo-location,location via Wi-Fi® signal triangulation, location via detecting a NFCbeacon signal that may indicate a particular location, and so forth.

In various example embodiments, one or more portions of the network 1880may be an ad hoc network, an intranet, an extranet, a virtual privatenetwork (VPN), a local area network (LAN), a wireless LAN (WLAN), a widearea network (WAN), a wireless WAN (WWAN), a metropolitan area network(MAN), the Internet, a portion of the Internet, a portion of the PublicSwitched Telephone Network (PSTN), a plain old telephone service (POTS)network, a cellular telephone network, a wireless network, a Wi-Fi®network, another type of network, or a combination of two or more suchnetworks. For example, the network 1880 or a portion of the network 1880may include a wireless or cellular network and the coupling 1882 may bea Code Division Multiple Access (CDMA) connection, a Global System forMobile communications (GSM) connection, or other type of cellular orwireless coupling. In this example, the coupling 1882 may implement anyof a variety of types of data transfer technology, such as SingleCarrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized(EVDO) technology, General Packet Radio Service (GPRS) technology,Enhanced Data rates for GSM Evolution (EDGE) technology, thirdGeneration Partnership Project (2GPP) including 2G, fourth generationwireless (4G) networks, Universal Mobile Telecommunications System(UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability forMicrowave Access (WiMAX), Long Term Evolution (LTE) standard, othersdefined by various standard setting organizations, other long rangeprotocols, or other data transfer technology.

The instructions 1816 may be transmitted or received over the network1880 using a transmission medium via a network interface device (e.g., anetwork interface component included in the communication components964) and utilizing any one of a number of well-known transfer protocols(e.g., Hypertext Transfer Protocol (HTTP)). Similarly, the instructions1816 may be transmitted or received using a transmission medium via thecoupling 1872 (e.g., a peer-to-peer coupling) to devices 1870. The term“transmission medium” shall be taken to include any intangible mediumthat is capable of storing, encoding, or carrying instructions 1816 forexecution by the machine 1800, and includes digital or analogcommunications signals or other intangible medium to facilitatecommunication of such software.

Modules, Components and Logic

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules may constitute eithersoftware modules (e.g., code embodied on a machine-readable medium or ina transmission signal) or hardware modules. A hardware module istangible unit capable of performing certain operations and may beconfigured or arranged in a certain manner. In example embodiments, oneor more computer systems (e.g., a standalone, client or server computersystem) or one or more hardware modules of a computer system (e.g., aprocessor or a group of processors) may be configured by software (e.g.,an application or application portion) as a hardware module thatoperates to perform certain operations as described herein.

In various embodiments, a hardware module may be implementedmechanically or electronically. For example, a hardware module maycomprise dedicated circuitry or logic that is permanently configured(e.g., as a special-purpose processor, such as a field programmable gatearray (FPGA) or an application-specific integrated circuit (ASIC)) toperform certain operations. A hardware module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that istemporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a hardware modulemechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations.

Accordingly, the term “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired) or temporarilyconfigured (e.g., programmed) to operate in a certain manner and/or toperform certain operations described herein. Considering embodiments inwhich hardware modules are temporarily configured (e.g., programmed),each of the hardware modules need not be configured or instantiated atany one instance in time. For example, where the hardware modulescomprise a general-purpose processor configured using software, thegeneral-purpose processor may be configured as respective differenthardware modules at different times. Software may accordingly configurea processor, for example, to constitute a particular hardware module atone instance of time and to constitute a different hardware module at adifferent instance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multipleof such hardware modules exist contemporaneously, communications may beachieved through signal transmission (e.g., over appropriate circuitsand buses) that connect the hardware modules. In embodiments in whichmultiple hardware modules are configured or instantiated at differenttimes, communications between such hardware modules may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware modules have access. Forexample, one hardware module may perform an operation, and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions. The modulesreferred to herein may, in some example embodiments, compriseprocessor-implemented modules.

Similarly, the methods described herein may be at least partiallyprocessor-implemented. For example, at least some of the operations of amethod may be performed by one or processors or processor-implementedmodules. The performance of certain of the operations may be distributedamong the one or more processors, not only residing within a singlemachine, but deployed across a number of machines. In some exampleembodiments, the processor or processors may be located in a singlelocation (e.g., within a home environment, an office environment or as aserver farm), while in other embodiments the processors may bedistributed across a number of locations.

The one or more processors may also operate to support performance ofthe relevant operations in a “cloud computing” environment or as a“software as a service” (SaaS). For example, at least some of theoperations may be performed by a group of computers (as examples ofmachines including processors), these operations being accessible via anetwork (e.g., the Internet) and via one or more appropriate interfaces(e.g., Application Program Interfaces (APIs).)

Electronic Apparatus and System

Example embodiments may be implemented in digital electronic circuitry,or in computer hardware, firmware, software, or in combinations of them.Example embodiments may be implemented using a computer program product,e.g., a computer program tangibly embodied in an information carrier,e.g., in a machine-readable medium for execution by, or to control theoperation of, data processing apparatus, e.g., a programmable processor,a computer, or multiple computers.

A computer program can be written in any form of programming language,including compiled or interpreted languages, and it can be deployed inany form, including as a stand-alone program or as a module, subroutine,or other unit suitable for use in a computing environment. A computerprogram can be deployed to be executed on one computer or on multiplecomputers at one site or distributed across multiple sites andinterconnected by a communication network.

In example embodiments, operations may be performed by one or moreprogrammable processors executing a computer program to performfunctions by operating on input data and generating output. Methodoperations can also be performed by, and apparatus of exampleembodiments may be implemented as, special purpose logic circuitry,e.g., a field programmable gate array (FPGA) or an application-specificintegrated circuit (ASIC).

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. Inembodiments deploying a programmable computing system, it will beappreciated that that both hardware and software architectures requireconsideration. Specifically, it will be appreciated that the choice ofwhether to implement certain functionality in permanently configuredhardware (e.g., an ASIC), in temporarily configured hardware (e.g., acombination of software and a programmable processor), or a combinationof permanently and temporarily configured hardware may be a designchoice. Below are set out hardware (e.g., machine) and softwarearchitectures that may be deployed, in various example embodiments.

Although the embodiments of the present invention have been describedwith reference to specific example embodiments, it will be evident thatvarious modifications and changes may be made to these embodimentswithout departing from the broader scope of the inventive subjectmatter. Accordingly, the specification and drawings are to be regardedin an illustrative rather than a restrictive sense. The accompanyingdrawings that form a part hereof show by way of illustration, and not oflimitation, specific embodiments in which the subject matter may bepracticed. The embodiments illustrated are described in sufficientdetail to enable those skilled in the art to practice the teachingsdisclosed herein. Other embodiments may be used and derived therefrom,such that structural and logical substitutions and changes may be madewithout departing from the scope of this disclosure. This DetailedDescription, therefore, is not to be taken in a limiting sense, and thescope of various embodiments is defined only by the appended claims,along with the full range of equivalents to which such claims areentitled.

Such embodiments of the inventive subject matter may be referred toherein, individually and/or collectively, by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed. Thus, although specific embodiments havebeen illustrated and described herein, it should be appreciated that anyarrangement calculated to achieve the same purpose may be substitutedfor the specific embodiments shown. This disclosure is intended to coverany and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent, to those of skill inthe art, upon reviewing the above description.

All publications, patents, and patent documents referred to in thisdocument are incorporated by reference herein in their entirety, asthough individually incorporated by reference. In the event ofinconsistent usages between this document and those documents soincorporated by reference, the usage in the incorporated referencesshould be considered supplementary to that of this document; forirreconcilable inconsistencies, the usage in this document controls.

In this document, the terms “a” or “an” are used, as is common in patentdocuments, to include one or more than one, independent of any otherinstances or usages of “at least one” or “one or more.” In thisdocument, the term “or” is used to refer to a nonexclusive or, such that“A or B” includes “A but not B,” “B but not A,” and “A and B,” unlessotherwise indicated. In the appended claims, the terms “including” and“in which” are used as the plain-English equivalents of the respectiveterms “comprising” and “wherein.” Also, in the following claims, theterms “including” and “comprising” are open-ended; that is, a system,device, article, or process that includes elements in addition to thoselisted after such a term in a claim are still deemed to fall within thescope of that claim.

What is claimed is:
 1. A remote computing system comprising: one or morehardware processors; at least one non-transitory machine-readable mediumstoring instructions that, when executed by the one or more processors,cause the one or more processors to perform operations including:accessing metadata generated by and communicated from a cameraconfigured to monitor one or more parking spaces, wherein the metadataincludes a set of pixel coordinates defining a location of a vehiclewithin an image captured by the camera but excludes the image; based atleast in part on a location of the camera, translating the set of pixelcoordinates to a first set of global coordinates defining a firstgeospatial location of a first blob-shaped object corresponding to thevehicle; accessing a second set of global coordinates defining a secondgeospatial location of a second blob-shaped object corresponding to aparking space having a defined boundary; determining an amount ofoverlap of the first blob-shaped object with the second blob-shapedobject based on a difference between the first set of global coordinatesand the second set of global coordinates; determining that the vehicleis parked within the defined boundary of the parking space when theamount of overlap satisfies a threshold; updating a data objectassociated with the vehicle to indicate the vehicle is parked in theparking space when the vehicle is determined to be parked within thedefined boundary of the parking space; and communicating an output to aclient device located remotely from the one or more processors when thevehicle is determined to be parked within the defined boundary of theparking space, the client device being associated with a user of thevehicle.
 2. The remote computing system of claim 1, wherein determiningthe amount of overlap comprises: computing a first centroid using thefirst set of global coordinates, the first centroid corresponding to anarithmetic mean position of all points of the vehicle defined by thefirst set of global coordinates; computing a second centroid using thesecond set of global coordinates, the second centroid corresponding toan arithmetic mean position of all points of the parking space definedby the second set of global coordinates; and determining a distancebetween the first centroid and the second centroid, the distancecorresponding to the amount of overlap.
 3. The remote computing systemof claim 2, wherein computing the first centroid includes calculatingthe arithmetic mean position of all points of the vehicle defined by thefirst set of global coordinates.
 4. The remote computing system of claim1, wherein translating the set of pixel coordinates to the first set ofglobal coordinates comprises: isolating a plurality of coordinate pairsof the set of pixel coordinates, wherein various ones of the pluralityof coordinate pairs represent one or more corners of a defined border ofthe vehicle; and translating the plurality of coordinate pairs intocorresponding coordinate pairs in a geospatial area.
 5. The remotecomputing system of claim 1, further comprising: determining anoccupancy status of the parking space based in part on determiningwhether the vehicle overlaps the parking space.
 6. The remote computingsystem of claim 5, wherein determining the occupancy status of theparking space comprises: determining whether the vehicle is stationarybased on a comparison of the first set of pixel coordinates with asecond set of pixel coordinates, the second set of pixel coordinatesdefining a second location of the vehicle in a second image.
 7. Theremote computing system of claim 1, wherein the camera is located on astreetlight.
 8. The remote computing system of claim 1, whereindetermining the amount of overlap includes: calculating a distancebetween the first geospatial location and the second geospatiallocation.
 9. A method comprising: capturing, by at least one cameramounted on a streetlight, an image; generating, by the at least onecamera, metadata associated with the image, the metadata including a setof pixel coordinates representing a position of a vehicle within theimage; communicating, by the at least one camera, the metadata but notthe image to a remote computing device; based at least in part on alocation of the at least one camera, translating, by the remotecomputing device, the set of pixel coordinates to a first set of globalcoordinates defining a first geospatial location of the vehicle;accessing, by the remote computing device, a second set of globalcoordinates defining a second geospatial location of a parking space;determining, by the remote computing device, an amount of overlap of thevehicle with the parking space based on a difference between the firstset of global coordinates and the second set of global coordinates; anddetermining, by the remote computing device, whether the vehicle isparked in the parking space based on the amount of overlap.
 10. Themethod of claim 9, wherein determining the amount of overlap includes:computing a first centroid using the first set of global coordinates,the first centroid corresponding to an arithmetic mean position of allpoints of the vehicle defined by the first set of global coordinates;computing a second centroid using the second set of global coordinates,the second centroid corresponding to an arithmetic mean position of allpoints of the parking space defined by the second set of globalcoordinates; and determining a distance between the first centroid andthe second centroid, the distance corresponding to the amount ofoverlap.
 11. The method of claim 9, wherein translating the set of pixelcoordinates to the first set of global coordinates comprises: isolatinga plurality of coordinate pairs of the set of pixel coordinates, whereinvarious ones of the plurality of coordinate pairs represent one or morecorners of the vehicle; and translating the plurality of coordinatepairs into corresponding coordinate pairs in a geospatial area.
 12. Themethod of claim 9, further comprising: determining an occupancy statusof the parking space based in part on determining whether the vehicleoverlaps the parking space.
 13. The method of claim 9, furthercomprising: defining a first location of the vehicle in a first imagebased on the set of pixel coordinates; defining a second location of thevehicle in a second image based on a second set of pixel coordinates;and determining whether the vehicle is stationary based on a comparisonof the set of pixel coordinates with the second set of pixelcoordinates.
 14. A non-transitory machine-readable storage medium, andembodying instructions that, when executed by one or more processors ofa machine, cause the machine to perform operations comprising: accessingmetadata generated by and communicated from a camera configured tomonitor one or more parking spaces, wherein the metadata includes a setof pixel coordinates defining a location of a vehicle within an imagecaptured by the camera but excludes the image; based at least in part ona location of the camera, translating the set of pixel coordinates to afirst set of global coordinates defining a first geospatial location ofthe vehicle; accessing a second set of global coordinates defining asecond geospatial location of a parking space having a defined boundary;determining an amount of overlap of the vehicle with the parking spacebased on a difference between the first set of global coordinates andthe second set of global coordinates; determining that the vehicle isparked within the defined boundary of the parking space when the amountof overlap satisfies a threshold; updating a data object associated withthe vehicle to indicate the vehicle is parked in the parking space whenthe vehicle is determined to be parked within the defined boundary ofthe parking space; and communicating an output to a client devicelocated remotely from the machine when the vehicle is determined to beparked within the defined boundary of the parking space, the clientdevice being associated with a user of the vehicle.
 15. Thenon-transitory machine-readable storage medium of claim 14, wherein thecamera is located on a streetlight.
 16. The non-transitorymachine-readable storage medium of claim 14, wherein the metadatafurther includes identification information representing the camera andtimestamp information representing a time associated with the image. 17.The non-transitory machine-readable storage medium of claim 14, whereinthe machine is located proximate a streetlight.